Mod 12 · Procurement

How security actually gets purchased.

Compliance changes why security is bought. Procurement changes how. Security review, legal review, risk committee, cyber-insurance gates, budget ownership, marketplace pathways, vendor-approval friction, board- and compliance-driven urgency — the operating procedures that turn a verbal yes into a signed PO.

Status · In progress

This module is being written. Will cover the seven gates that block or accelerate a security purchase: security review · legal review · risk committee · cyber-insurance approval · budget ownership · marketplace purchasing · vendor-approval friction — plus the two urgency engines: compliance-driven and board-driven. Sits next to Compliance and feeds the Triggers mapping.