Interdependencies between essential and important entities
ENISA Interdependencies Indicators Tool
| ISO IEC 27002 control name | EXAMPLE OF IMPLEMENTATION |
|---|---|
Access control policy
An access control policy should be established, documented and reviewed based on business and information security requirements. |
Access control elements (e.g ACLs, whitelists) provide information on the number of potential affected users; especially focus on connected users to an interdependent service. |
Removal or adjustment of access rights
The access rights of all employees and external party users to information and information processing facilities should be removed upon termination of their employment, contract or agreement, or adjusted upon change. |
Check the number of the users that a adjustement of access rights is requested, especially for an external service. |
Management of secret authentication information of users
The allocation of secret authentication information should be controlled through a formal management process. |
Check the number of signed user statements for keeping personal secret authentication information by the corporate IT system. Take into account external users as well as users of shared or common accounts. |
Use of secret authentication information
Users should be required to follow the organisation’s practices in the use of secret authentication information. |
Check the number of signed user statements for keeping personal secret authentication information by the corporate IT system. Take into account external users as well as users of shared or common accounts. |
Review of user access rights
Asset owners should review users’ access rights at regular intervals. |
The review of access rights provides information on the number of potential affected users per system / service / software. |
User access provisioning
A formal user access provisioning process should be implemented to assign or revoke access rights for all user types to all systems and services. |
User Access Management provides information on the number of potential affected users; especially focus on connected users to an interdependent service. |
Management of privileged access rights
The allocation and use of privileged access rights should be restricted and controlled. |
Check the number of requests for privileged access to a service / system / software. |
User registration and de-registration
A formal user registration and de-registration process should be implemented to enable assignment of access rights. |
Check the number of requests for access to an interdependent service |
Restrictions on software installation
Rules governing the installation of software by users should be established and implemented. |
By reviewing the number of users that have access to speicific software, the organisation may determine the number of affected users in a NIS incident. |
Controls against malware
Detection, prevention and recovery controls to protect against malware should be implemented, combined with appropriate user awareness. |
Use network traffic (registeres IPs) or registered users of antimalware systems (e.g. IDS, centrally managed antivirus, DLP) to figure out the number of potential incident affected users of an interdependent service. |
Event logging
Event logs recording user activities, exceptions, faults and information security events should be produced, kept and regularly reviewed. |
Check the logs of a service to figure out the number of potential affected users. |
Documented operating procedures
Operating procedures should be documented and made available to all users who need them. |
Use network traffic (registeres IPs) or registered users of antimalware systems (e.g. IDS, centrally managed antivirus, DLP) to figure out the number of potential incident affected users of an interdependent service. |