Control access to services based on knowledge of users and devices

The organisation must manage all of it’s users and their privileges. This includes all third party users, which have access into the organisations data or systems.

The organisation must remove users entirely or remove privileges from them when they are no longer needed e.g when employee role changes.

The organization implements role-based access control with predefined access roles for the various protected assets that entitle access to the associated asset. Strictness of the access roles should reflect the security risks associated with the asset.

The following should be considered to support access management:

• how much information each user needs access to
• how widely the user should be able to edit data (read, write, delete, print, execute)
• whether other applications have access to the data
• whether the data can be segregated within the property so that sensitive data is less exposed

Control access to services based on knowledge of users and devices.

One example is if a user logs in via an unmanaged device (the organisation trusts the user but does not control the device) and gains access to fewer services than if the user logs in via an organisation-managed device (the organisation knows both the user and the device).

To ensure that authorized users have access to data systems and to prevent unauthorized access, the organization has defined formal processes for:

• User registration and deletion
• Allocation of access rights
• Reassessment of access rights
• Deleting or changing access rights

The implementation of these things must always take place through a defined, formal process.