2 of 13

The October 2026 landscape

Learn what each kind of document is for, and what it cannot prove.

You have the rule. These documents name risks and organize decisions. None of them is proof that your system follows the rule.

Part 1 of 5, then one check

Documents

A list, a framework, and a specification are not the same thing.

OWASP is the Open Worldwide Application Security Project, a community that publishes security guidance. NIST is the U.S. National Institute of Standards and Technology. You will see both names often. They do different jobs.

A risk list names common failures. OWASP’s agentic list and its large-language-model list do that. A framework organizes decisions and owners. NIST’s AI Risk Management Framework and Cybersecurity Framework do that. A guide explains practice. A specification defines how a protocol must behave.

A protocol is an agreed set of rules two programs use to understand each other. MCP authorization text and OAuth security documents are specifications. The title does not make any of these mandatory. Requirements come from law, contract, policy, or a standard you choose to adopt.

A draft is still changing. Beta means an early release for feedback. A pinned version is the exact release you reviewed. A later edition can change both the advice and the requirements. Compliance means you met a requirement that applies to you. Certification is a formal assessment under a defined scheme. Reading a list is neither.

Course