Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.
Plan for regular backups of all the organisation’s data. As a minimum, the plan should describe: a) Which data should be backed up. b) Frequency of backups of various data, based on value. c) Responsibility for backing up various data. d) Procedures for failed backups. e) How long to store backups. f) Logical and physical criteria for backup security. g) Criteria for how long it should take to restore the organisation’s systems and data (see principle 4.1 – “Prepare the organisation for incident”). h) The roles responsible for approving the plan.
Plan for regular backups of all the organisation’s data. As a minimum, the plan should describe: a) Which data should be backed up. b) Frequency of backups of various data, based on value. c) Responsibility for backing up various data. d) Procedures for failed backups. e) How long to store backups. f) Logical and physical criteria for backup security. g) Criteria for how long it should take to restore the organisation’s systems and data (see principle 4.1 – “Prepare the organisation for incident”). h) The roles responsible for approving the plan.
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.
