Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.
Establish a process to identify devices and software in use at the organisation. One should ideally use automated and centralised tools to detect and monitor devices and software and to determine which software is running on which devices. The inventory should also include ownership, older unsupported products (should be explicitly identified) as well as devices and software not connected to the organisation’s network (e.g. USB devices). More details in 1.2.3 (devices) and 1.2.4 (software).
Establish a process to identify devices and software in use at the organisation. One should ideally use automated and centralised tools to detect and monitor devices and software and to determine which software is running on which devices. The inventory should also include ownership, older unsupported products (should be explicitly identified) as well as devices and software not connected to the organisation’s network (e.g. USB devices). More details in 1.2.3 (devices) and 1.2.4 (software).
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.
.svg)
.svg)
.svg)
Break down the framework into specific obligations that must be met.
.svg)
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.
