2.6.2: Establish a formal process for administration of accounts, access rights and privileges

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

Establish a formal process for administration of accounts, access rights and privileges. a) The process should cover i) accounts for users, devices and system processes, ii) access rights to systems and applications, iii) privileges in relation to operating systems (e.g. admin privileges) and the organisation’s shared user database. b) The process should include the entire life cycle and cover creation, maintenance and deactivation. Deactivate rather than delete accounts and access rights in order that there is an audit trail in accordance with prevailing laws and regulations. c) The guidelines on access control (2.6.1) and the process for administering accounts, access rights and privileges (2.6.2.a) should be documented and communicated across the organisation.

This requirement is part of the framework:  
NSM ICT Security Principles (Norway)
Best practices
How to implement:
2.6.2: Establish a formal process for administration of accounts, access rights and privileges
This policy on
2.6.2: Establish a formal process for administration of accounts, access rights and privileges
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.

Establish a formal process for administration of accounts, access rights and privileges. a) The process should cover i) accounts for users, devices and system processes, ii) access rights to systems and applications, iii) privileges in relation to operating systems (e.g. admin privileges) and the organisation’s shared user database. b) The process should include the entire life cycle and cover creation, maintenance and deactivation. Deactivate rather than delete accounts and access rights in order that there is an audit trail in accordance with prevailing laws and regulations. c) The guidelines on access control (2.6.1) and the process for administering accounts, access rights and privileges (2.6.2.a) should be documented and communicated across the organisation.

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
2.6.2: Establish a formal process for administration of accounts, access rights and privileges
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
2.6.2: Establish a formal process for administration of accounts, access rights and privileges
of the framework  
NSM ICT Security Principles (Norway)
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
Document the identity life cycle management processes
Critical
High
Normal
Low
2
requirements
System management
Access control and authentication

Document the identity life cycle management processes

This task helps you comply with the following requirements

Descriptions of different access rights management processes
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.