Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.
Deactivate unnecessary functionality. Consider deactivating built-in functions (in both operating systems and applications) on clients, servers and network equipment not needed by the organisation in order to reduce the attack surface. This could include i) older or unused protocols, ii) built-in support for personal cloud services, for example, iii) other built-in services that the organisation will not be using.
Deactivate unnecessary functionality. Consider deactivating built-in functions (in both operating systems and applications) on clients, servers and network equipment not needed by the organisation in order to reduce the attack surface. This could include i) older or unused protocols, ii) built-in support for personal cloud services, for example, iii) other built-in services that the organisation will not be using.
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.
