Appendix D. Glossary

A number of terms in this book are used very loosely out there in the world. I provide this small glossary to pin things down a bit more.

Artifact (especially, software artifact)—

Those documents and objects created in the course of building software. The touchpoints in this book are software security best practices meant to be applied to common software artifacts including requirements, use cases, design documents, architecture documents, test plans, test results, code, executables, and feedback from the field.

Attack pattern—

Like a design pattern, only applicable to attacks. A high-level description of a set of software attacks. See Chapter 8.

Bug—

A bug is an implementation-level software problem. Bugs may exist in code but ...

Get Software Security: Building Security In now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.