Skip to main content
MuonPartners
Services
Architecture

Solution design and technology roadmapping

Solution AssessmentTechnology RoadmapsIntegration DesignSolution ArchitectureTechnical Design
Cyber Security

Security assessments, IAM, and compliance

AssessmentsIAMComplianceSecurity BaselineCyber Innovation
Network and Platform

Network architecture and cloud platforms

Network DesignCloud StrategyModernisation
Enterprise Architecture

Business-technology alignment

Business AlignmentPortfolio AnalysisGovernance
View all services
ProjectsCase StudiesInsightsToolsAbout
Contact Us

Services

Architecture
Solution AssessmentTechnology RoadmapsIntegration DesignSolution ArchitectureTechnical Design
Cyber Security
AssessmentsIAMComplianceSecurity BaselineCyber Innovation
Network and Platform
Network DesignCloud StrategyModernisation
Enterprise Architecture
Business AlignmentPortfolio AnalysisGovernance
ProjectsCase StudiesInsightsToolsAboutContact
Get in Touch
MuonPartners

Strategic technology consulting for Australian organisations navigating complexity.

Services

  • Architecture
  • Cyber Security
  • Network and Platform
  • Enterprise Architecture

Company

  • About
  • Products
  • Frameworks
  • Cross-Framework Mapping
  • Projects
  • Case Studies
  • Insights
  • Contact

Contact

  • [email protected]
  • Australia
  • LinkedIn

© 2026 Muon Partners. All rights reserved.

ABN 50 669 022 315 · A Muon Group company.

Privacy PolicyTerms of Service
  1. Frameworks
  2. >C2M2
  3. >Situational Awareness
  4. >Situational Awareness - Objective 2
  5. >C2M2-SITUATION-2C
C2M2-SITUATION-2CActive

Monitoring and analysis requirements are established and maintained for the function and address timely review of event data

Statement

Monitoring and analysis requirements are established and maintained for the function and address timely review of event data

Location

Domain
Situational Awareness
Objective
Situational Awareness - Objective 2

Practice Details

Identifier
C2M2-SITUATION-2C
Domain
Situational Awareness
Objective
Objective 2
Maturity Level
MIL-2

Help Text

Monitoring and analysis requirements define the activities needed to provide information to stakeholders across the function on a regular basis to protect and sustain IT, OT, and information assets essential for the delivery of the function. The development of requirements should identify key stakeholders and how the monitoring and analysis requirements will satisfy their information needs. Monitoring requirements may be different for assets such as operations technology, field devices, mobile devices, virtualized assets, and assets residing in the cloud. The requirements should describe what data should be collected and how it should be analyzed. Requirements should also specify time parameters for review of collected data and how the data will be distributed. Requirements should consider: · type of data and extent of data necessary · the granularity of data necessary · the format(s) of the data · the distribution frequency of the data · how the data will be distributed · the retention of the data · how often reviews should be performed

Related Practices · Progression: This practice is part of a practice progression. Practice progressions are groups of related practices that represent increasingly complete or more advanced implementations of an activity. The practices in this progression include: SITUATION-2a, SITUATION-2b, SITUATION-2c, SITUATION-2f, SITUATION-2g.

AESCSF
AESCSF-SITUATION-2cequivalentvia derived-shared-practice-structure
View in graphReport an issue
← Back to Situational Awareness - Objective 2
Situational Awareness - Objective 29 controls
C2M2-SITUATION-2APeriodic reviews of log data or other cybersecurity monitoring activities are performed, at least in an ad hoc mannerC2M2-SITUATION-2BData and alerts from network and host monitoring infrastructure assets are periodically reviewed, at least in an ad hoc mannerC2M2-SITUATION-2CMonitoring and analysis requirements are established and maintained for the function and address timely review of event dataC2M2-SITUATION-2DIndicators of anomalous activity are established and maintained based on system logs, data flows, network baselines, cybersecurity events, and architecture and are monitored across the IT and OT environmentsC2M2-SITUATION-2EAlarms and alerts are configured and maintained to support the identification of cybersecurity eventsC2M2-SITUATION-2FMonitoring activities are aligned with the threat profile (THREAT-2e)C2M2-SITUATION-2GMore rigorous monitoring is performed for higher priority assetsC2M2-SITUATION-2HRisk analysis information (RISK-3d) is used to identify indicators of anomalous activityC2M2-SITUATION-2IIndicators of anomalous activity are evaluated and updated periodically and according to defined triggers, such as system changes and external events