NOTICE: Due to a lapse in annual appropriations, most of this website is not being updated. Learn more.
Form submissions will still be accepted but will not receive responses at this time. Sections of this site for programs using non-appropriated funds (such as NVLAP) or those that are excepted from the shutdown (such as CHIPS and NVD) will continue to be updated.
An official website of the United States government
Here’s how you know
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock (
) or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.
The Model Made Me Do It! A Cautionary Tale from a Security Control Baseline Tool Developer
Published
Author(s)
Joshua Lubell
Abstract
Even the best written specifications can be complicated documents to read and understand. Normative prose is often supported by tables and diagrams intended to clarify the specification. What happens when a tool developer interprets those clarifying features as implying a different model than the normative prose intends? What does this say about relying on derived data models in the tools that support the specification? A cautionary tale involving the security control baselines from the National Institute of Standards and Technology Special Publication 800-53 provides some answers — and insights.
Lubell, J.
(2021),
The Model Made Me Do It! A Cautionary Tale from a Security Control Baseline Tool Developer, Proceedings of Balisage: The Markup Conference, Washington, DC, US, [online], https://doi.org/10.4242/BalisageVol26.Lubell01, https://tsapps.nist.gov/publication/get_pdf.cfm?pub_id=932872
(Accessed October 8, 2025)