Construct · 1 fields · 1 citations

memory safety: a standalone construct

One name. One construct. A landmark on the map.

● anchor · a standalone construct Nearest construct by meaning·not indexed
memorysafety1 CONSTRUCTMemory safetySZEKERES · COMPUTER SECURITY

A single standalone construct; nearby constructs are located against it in the Collider. Tap a field for its definition, unit, and measures.

Computer security

the property that a program never accesses memory outside the bounds or lifetime of the objects it refers to, framed as a layered model of defenses.

In computer security, memory safety refers to the property that a program never accesses memory outside the bounds or lifetime of the objects it refers to, framed as a layered model of defenses. This meaning comes from Szekeres (2013) in 2013 IEEE Symposium on Security and Privacy.[1]

Unit
Recovery means
Measured by

Next

Run it through the Collider, or take the citations with you.

See how memory safety sits against neighbouring constructs in the Collider, or export every reference on this page in one click.

Open in ColliderExport BibTeXReport this entry

Nearby constructs

memory corruption attack1 fields · 1 citationsanchor · a standalone constructdata-oriented programming1 fields · 1 citationsanchor · a standalone constructmemory6 fields · 18 citationsjingle · one name, six constructs

References

  1. Szekeres, L., Payer, M., Tao Wei, & Song, D. (2013). SoK: Eternal War in Memory. 2013 IEEE Symposium on Security and Privacy. https://doi.org/10.1109/sp.2013.13

Cited on this page?

Confirm your construct, or correct us.

If your work is cited behind one of these entries, you know better than we do whether we captured the meaning right. Confirm it, suggest an edit, or dispute it, and your name goes on the entry as an author who has checked it, linked to your ORCID.

Claim your construct