Construct · 1 fields · 1 citations

software vulnerability honeymoon effect: a standalone construct

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

● anchor · a standalone construct Nearest construct by meaning·not indexed
software vulnerabilityhoneymoon effect1 CONSTRUCTSoftware vulnerabilityCLARK · SECURITY ECONOMICS

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

Security economics

the finding that newly released software enjoys a longer delay before its first exploited vulnerability than later versions, with legacy code shortening it.

In security economics, software vulnerability honeymoon effect refers to the finding that newly released software enjoys a longer delay before its first exploited vulnerability than later versions, with legacy code shortening it. This meaning comes from Clark (2010) in Proceedings of the 26th Annual Computer Security Applications Conference.[1]

Unit
Recovery means
Measured by

Next

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

See how software vulnerability honeymoon effect 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

code3 fields · 6 citationsjingle · one word, three constructseconomics of information security1 fields · 1 citationsanchor · a standalone constructsecurity3 fields · 3 citationsjingle · one word, three constructs

References

  1. Clark, S., Frei, S., Blaze, M., & Smith, J. (2010). Familiarity breeds contempt: the honeymoon effect and the role of legacy code in zero-day vulnerabilities. Proceedings of the 26th Annual Computer Security Applications Conference. https://doi.org/10.1145/1920261.1920299

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