17 §: Bevarande av journalhandlingar

Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.

En journalhandling ska bevaras minst tio år efter det att den sista uppgiften fördes in i handlingen. Regeringen eller den myndighet som regeringen bestämmer får meddela föreskrifter om att vissa slags journalhandlingar ska bevaras under längre tid än tio år.

See how Cyberday guides you to fulfill this requirement:
This requirement is part of the framework:  
Patientdatalag 2008:355 (Sverige)
Best practices
How to implement:
17 §: Bevarande av journalhandlingar
This policy on
17 §: Bevarande av journalhandlingar
provides a set concrete tasks you can complete to secure this topic. Follow these best practices to ensure compliance and strengthen your overall security posture.

En journalhandling ska bevaras minst tio år efter det att den sista uppgiften fördes in i handlingen. Regeringen eller den myndighet som regeringen bestämmer får meddela föreskrifter om att vissa slags journalhandlingar ska bevaras under längre tid än tio år.

Read below what concrete actions you can take to improve this ->
Frameworks that include requirements for this topic:
No items found.

How to improve security around this topic

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.

Here's a list of tasks that help you improve your information and cyber security related to
17 §: Bevarande av journalhandlingar
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
No other tasks found.

How to comply with this requirement

In Cyberday, requirements and controls are mapped to universal tasks. Each requirement is fulfilled with one or multiple tasks.

Here's a list of tasks that help you comply with the requirement
17 §: Bevarande av journalhandlingar
of the framework  
Patientdatalag 2008:355 (Sverige)
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
Data system listing and owner assignment
Critical
High
Normal
Low
107
requirements
System management
Data system management

Data system listing and owner assignment

Completing this task also progresses your compliance in all of the following frameworks and requirements. Cyberday automatically maps completed tasks to all of these current and future frameworks - so you do not have to do it again!

Data store listing and owner assignment
Critical
High
Normal
Low
91
requirements
Privacy
Processing principles and accountability

Data store listing and owner assignment

Completing this task also progresses your compliance in all of the following frameworks and requirements. Cyberday automatically maps completed tasks to all of these current and future frameworks - so you do not have to do it again!

Documentation of data sets for data stores
Critical
High
Normal
Low
97
requirements
Management of data sets
Management of data sets

Documentation of data sets for data stores

Completing this task also progresses your compliance in all of the following frameworks and requirements. Cyberday automatically maps completed tasks to all of these current and future frameworks - so you do not have to do it again!

Retention policy for medical records (Sweden)
Critical
High
Normal
Low
1
requirements
Management of data sets
Management of data sets

Retention policy for medical records (Sweden)

Completing this task also progresses your compliance in all of the following frameworks and requirements. Cyberday automatically maps completed tasks to all of these current and future frameworks - so you do not have to do it again!

Defining and documenting retention times for data sets
Critical
High
Normal
Low
28
requirements
Privacy
Processing principles and accountability

Defining and documenting retention times for data sets

Completing this task also progresses your compliance in all of the following frameworks and requirements. Cyberday automatically maps completed tasks to all of these current and future frameworks - so you do not have to do it again!

The ISMS component hierachy

When building an ISMS, it's important to understand the different levels of information hierarchy. Here's how Cyberday is structured.

Framework

Sets the overall compliance standard or regulation your organization needs to follow.

Requirements

Break down the framework into specific obligations that must be met.

Tasks

Concrete actions and activities your team carries out to satisfy each requirement.

Policies

Documented rules and practices that are created and maintained as a result of completing tasks.

Never duplicate effort. Do it once - improve compliance across frameworks.

Reach multi-framework compliance in the simplest possible way
Security frameworks tend to share the same core requirements - like risk management, backup, malware, personnel awareness or access management.
Cyberday maps all frameworks’ requirements into shared tasks - one single plan that improves all frameworks’ compliance.
Do it once - we automatically apply it to all current and future frameworks.