Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.
Use a centralised tool to manage accounts, access rights and privileges. a) Ideally, one should manage accounts, access rights and privileges for as many of the organisation’s resources as possible (cf. 2.6.2.a) using just a single tool for the entire organisation. b) Use the tool to keep track of all accounts, access rights and privileges. The tool should be able to perform as many of the tasks described in 2.6.1 as possible. c) When creating individual accounts (e.g. for contractors), one should set preliminary dates for deactivation. d) Deactivate or delete accounts that have not been used for a while (possibly with the exception of supplier maintenance accounts, for example). e) Use a centralised tool to check password quality against the organisation’s security requirements. As a minimum, avoid using common words and names in Norwegian and English as well as years and seasons.
Use a centralised tool to manage accounts, access rights and privileges. a) Ideally, one should manage accounts, access rights and privileges for as many of the organisation’s resources as possible (cf. 2.6.2.a) using just a single tool for the entire organisation. b) Use the tool to keep track of all accounts, access rights and privileges. The tool should be able to perform as many of the tasks described in 2.6.1 as possible. c) When creating individual accounts (e.g. for contractors), one should set preliminary dates for deactivation. d) Deactivate or delete accounts that have not been used for a while (possibly with the exception of supplier maintenance accounts, for example). e) Use a centralised tool to check password quality against the organisation’s security requirements. As a minimum, avoid using common words and names in Norwegian and English as well as years and seasons.
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.
