Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.
MIL1 requirements
a. Configuration baselines are established, at least in an ad hoc manner
MIL2 requirements
b. Configuration baselines are used to configure assets at deployment and restoration
c. Configuration baselines incorporate applicable requirements from the cybersecurity architecture (ARCHITECTURE-1f)
d. Configuration baselines are reviewed and updated periodically and according to defined triggers, such as system changes and changes to the cybersecurity architecture
MIL3 requirements
e. Asset configurations are monitored for consistency with baselines throughout the assets’ lifecycles
MIL1 requirements
a. Configuration baselines are established, at least in an ad hoc manner
MIL2 requirements
b. Configuration baselines are used to configure assets at deployment and restoration
c. Configuration baselines incorporate applicable requirements from the cybersecurity architecture (ARCHITECTURE-1f)
d. Configuration baselines are reviewed and updated periodically and according to defined triggers, such as system changes and changes to the cybersecurity architecture
MIL3 requirements
e. Asset configurations are monitored for consistency with baselines throughout the assets’ lifecycles
In Cyberday, requirements and controls are mapped to universal tasks. A set of tasks in the same topic create a Policy, such as this one.
In Cyberday, requirements and controls are mapped to universal tasks. Each requirement is fulfilled with one or multiple tasks.
When building an ISMS, it's important to understand the different levels of information hierarchy. Here's how Cyberday is structured.
Sets the overall compliance standard or regulation your organization needs to follow.
Break down the framework into specific obligations that must be met.
Concrete actions and activities your team carries out to satisfy each requirement.
Documented rules and practices that are created and maintained as a result of completing tasks.