Identify and document security requirements for developed software, considering customer obligations, regulatory expectations, internal policy, and known threats. Make the requirements accessible to development teams and update them as the threat landscape changes.
NIST SP 800-218 218-PO.1.1 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-218 your existing evidence covers. Hold NIST SP 800-53 Rev 5 and 30 of 42 NIST SP 800-218 controls already carry evidence.
Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the NIST SP 800-53 Rev 5 pair alone.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.