5.16: Identiteitsbeheer

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

De organisatie moet de volledige levenscyclus van identiteiten actief beheren om personen en systemen die toegang hebben tot informatie en activa van de organisatie op unieke wijze te kunnen identificeren. Individuele identiteiten moeten op unieke wijze aan één persoon worden gekoppeld om de verantwoordelijkheid voor hun handelingen te kunnen garanderen. Gedeelde identiteiten die aan meerdere personen worden toegewezen, zijn alleen toegestaan wanneer dit om zakelijke of operationele redenen noodzakelijk is. Deze moeten specifiek worden goedgekeurd en gedocumenteerd.

Zorgspecifieke controlemaatregel (aanvullend)

Gebruikers die toegang willen tot persoonlijke gezondheidsinformatie en andere vertrouwelijke informatie moeten formeel worden geregistreerd.

This requirement is part of the framework:  
NEN 7510 - Informatiebeveiliging in de zorg (Nederlands)

Other requirements of the framework

47324
5.16: Identiteitsbeheer
No items found.
Best practices
How to implement:
5.16: Identiteitsbeheer
This policy on
5.16: Identiteitsbeheer
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.

De organisatie moet de volledige levenscyclus van identiteiten actief beheren om personen en systemen die toegang hebben tot informatie en activa van de organisatie op unieke wijze te kunnen identificeren. Individuele identiteiten moeten op unieke wijze aan één persoon worden gekoppeld om de verantwoordelijkheid voor hun handelingen te kunnen garanderen. Gedeelde identiteiten die aan meerdere personen worden toegewezen, zijn alleen toegestaan wanneer dit om zakelijke of operationele redenen noodzakelijk is. Deze moeten specifiek worden goedgekeurd en gedocumenteerd.

Zorgspecifieke controlemaatregel (aanvullend)

Gebruikers die toegang willen tot persoonlijke gezondheidsinformatie en andere vertrouwelijke informatie moeten formeel worden geregistreerd.

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
5.16: Identiteitsbeheer
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
5.16: Identiteitsbeheer
of the framework  
NEN 7510 - Informatiebeveiliging in de zorg (Nederlands)
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
Process for removing hardware and access rights at termination of employment relationship
Critical
High
Normal
Low
44
requirements
Personnel security
Changes in employment relationships

Process for removing hardware and access rights at termination of employment relationship

This task helps you comply with the following requirements

Process for granting access rights at the start of employment relationships
Critical
High
Normal
Low
14
requirements
Personnel security
Changes in employment relationships

Process for granting access rights at the start of employment relationships

This task helps you comply with the following requirements

Registration of users accessing PHI
Critical
High
Normal
Low
1
requirements
System management
Access control and authentication

Registration of users accessing PHI

This task helps you comply with the following requirements

Access to electronic protected health information
Critical
High
Normal
Low
Access requests to PHI
Critical
High
Normal
Low
2
requirements
Privacy
Informing and data subject requests

Access requests to PHI

This task helps you comply with the following requirements

Document the identity life cycle management processes
Critical
High
Normal
Low
3
requirements
System management
Access control and authentication

Document the identity life cycle management processes

This task helps you comply with the following requirements

Avoiding and documenting shared user accounts
Critical
High
Normal
Low

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.