An autonomous vehicle fleet management enterprise is restructuring its security management oversight framework following an external compliance review. Match each security governance document type on the left with its corresponding organizational function and enforcement authority on the right.
- Acceptable Use PolicyMandatory high-level administrative directive defining legal boundaries and rules for using organizational assets.
- Technical Security StandardMandatory requirement specifying uniform technology selections, protocols, and encryption algorithms across systems.
- System Security BaselineMandatory minimum hardened configuration build required for a specific platform before entering production.
- Operational Security GuidelineDiscretionary recommendations and best-practice advice providing flexibility during implementation.
Answer
Acceptable Use Policy matches mandatory high-level administrative directive defining legal boundaries for using assets; Technical Security Standard matches mandatory requirement specifying uniform technology selections and protocols; System Security Baseline matches mandatory minimum hardened configuration build required prior to production deployment; Operational Security Guideline matches discretionary recommendations providing flexibility.
Each item correctly aligns with its precise position in the governance documentation hierarchy: policies set compulsory behavioral rules, standards dictate uniform technical controls, baselines set mandatory minimum deployment configurations, and guidelines provide non-mandatory advice.
Step-by-Step Solution
Key Concept
Security Governance Documentation Hierarchy