MCMMCM DocsEngineering (Internal)
HLDModulesSecOps
v1.2 is unreleased — see v1.1 for the current stable release.

MBSS Compliance

Minimum Baseline Security Standards — the cloud security control framework enforced by MCM SecOps.

MBSS Compliance

MBSS (Minimum Baseline Security Standards) Compliance defines the minimum required security controls that every system, cloud account, application, or infrastructure must comply with. It functions as a baseline security framework covering IAM, networking, logging, encryption, monitoring, and vulnerability management.

MBSS is similar in spirit to CIS Benchmarks, NIST 800-53, or ISO 27001 Annex A controls — but is typically customised per organisation.


Control Domains

1. Identity & Access

ControlDescription
MFA enabledAll users must have multi-factor authentication active
No root-user usageRoot/admin accounts must not be used for day-to-day operations
Least privilegeIAM roles and policies must follow the principle of least privilege
Strong password policyMinimum length, complexity, and rotation requirements enforced

2. Network & Perimeter Security

ControlDescription
No open portsUnnecessary ports must be closed on all security groups / firewalls
Restricted inbound/outbound rulesOnly explicitly required traffic is permitted
Traffic logging enabledVPC Flow Logs or Azure NSG Flow Logs must be active

3. Logging & Monitoring

ControlDescription
CloudTrail / Activity Logs enabledCloud audit logs must be active for all accounts
Centralised log retentionLogs must be retained for a defined period in a central store
Alerts for key eventsAlerts on IAM changes, root login, policy violations

4. Encryption

ControlDescription
Storage encrypted at restS3, EBS, RDS, and equivalent Azure storage must use encryption
TLS 1.2+ enforcedAll data in transit must use TLS 1.2 or higher

5. Resource Configuration

ControlDescription
Mandatory tagsAll resources must have owner and cost-center tags
Backups enabledBackup policies must be active for databases and critical storage
Versioning enabledS3 buckets and equivalent storage must have versioning where applicable

6. Vulnerability & Patch Management

ControlDescription
Regular scanningAll hosts and containers must be scanned on a defined schedule
OS patch complianceOperating systems must be on a supported and patched version

7. Governance Rules

ControlDescription
Naming standardsCloud resources must follow organisational naming conventions
Region restrictionsResources must only be provisioned in approved regions
Resource guardrailsPolicies prevent creation of non-compliant resource configurations

Summary

MBSS represents the baseline operational and security controls needed to ensure cloud accounts meet a minimum safe configuration. MCM enforces these controls through the combination of Cloud Custodian (cloud-level configuration policies) and Wazuh (host-level and runtime compliance checks).

On this page