What this control covers
Issues specially configured systems for high-risk travel locations and applies controls upon return to mitigate increased threats. This control supports the High-Risk Configuration System capability within the Configuration Management family.
Why it matters
Risk is the language an executive team understands; this control connects technical reality to board-level decisions and budget allocation.
How to implement
AWS
Codify the policy intent as SCPs, AWS Config conformance packs, and Security Hub standards so the cloud enforces what the document says.
Azure
Codify in Azure Policy initiatives (built-in regulatory compliance for CIS, ISO 27001, SOC 2, HIPAA) and assign at management-group level.
GCP
Org Policy Service for guardrails and Config Validator in CI to pre-check Terraform plans against policy as code (Rego).
On-premises
Maintain a policy library with a documented review cadence (annual minimum); store in your GRC tool with attestation tracking. Map each policy to controls so an audit pull cites the exact policy clause.
Evidence to collect
infra_scan— See the iCompaas Evidence library for the canonical source for this evidence type.
Infrastructure posture tooling (AWS Config, Azure Policy, Nessus) verifies platform hardening. Focus: Configure Systems And Components For High-Risk Areas.
Quick checklist
- Security — Management / System
- Configuration — Management / System
- Network — Management / System
- System — Management / System
- Control — Management / System
- Configure — Management / System
Related articles on this site
- Microsoft Cloud Security Posture Management (CSPM)
- NIST 800-171 3.4.2 Establish and enforce security configuration settings for information technology products employed in organizational systems.
- NIST 800-171 3.12.1 Periodically assess the security controls in organizational systems to determine if the controls are effective in their application.
- NIST 800-171 3.8.7 Control the use of removable media on system components.