Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.
Minimise privileges for end users and special users. a) Do not assign administrator privileges to end users. b) Manage special users (e.g. developers) who may exceptionally need extended system privileges, including administrative privileges. Each special user should have two separate accounts: one for ordinary office use such as email and internet searches, and one for tasks requiring elevated privileges. There should be adequate security barriers between these two accounts and, as an absolute minimum, they must not have the same password.
Minimise privileges for end users and special users. a) Do not assign administrator privileges to end users. b) Manage special users (e.g. developers) who may exceptionally need extended system privileges, including administrative privileges. Each special user should have two separate accounts: one for ordinary office use such as email and internet searches, and one for tasks requiring elevated privileges. There should be adequate security barriers between these two accounts and, as an absolute minimum, they must not have the same password.
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.
