Construct · 1 fields · 1 citations

security smells in infrastructure as code: a standalone construct

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

● anchor · a standalone construct Nearest construct by meaning·not indexed

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

Software engineering

recurring coding patterns in infrastructure scripts, such as hard-coded secrets or weak cryptography, that signal security weakness.

In software engineering, security smells in infrastructure as code refers to recurring coding patterns in infrastructure scripts, such as hard-coded secrets or weak cryptography, that signal security weakness. This meaning comes from Rahman (2019) in 2019 IEEE/ACM 41st International Conference on Software Engineering (ICSE).[1]

Unit
Recovery means
Measured by

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

See how security smells in infrastructure as code sits against neighbouring constructs in the Collider, or export every reference on this page in one click.

Open in Collider Export BibTeX Report this entry

Nearby constructs

code3 fields · 6 citationsjingle · one word, three constructs security3 fields · 3 citationsjingle · one word, three constructs signal5 fields · 5 citationsjingle · one word, five constructs

References

Rahman, A., Parnin, C., & Williams, L. (2019). The Seven Sins: Security Smells in Infrastructure as Code Scripts. 2019 IEEE/ACM 41st International Conference on Software Engineering (ICSE). https://doi.org/10.1109/icse.2019.00033

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