ISO 27001 Annex : A.9.2.3 Management of Privileged Access Rights & A.9.2.4 Management of Secret Authentication Information of Users

ISO 27001 Annex : A.9.2.3 Management of Privileged Access Rights & A.9.2.4 Management of Secret Authentication Information of Users

ISO 27001 Annex : A.9.2.3 Management of Privileged Access Rights & A.9.2.4 Management of Secret Authentication Information of Users these two topic is explained in this article.

A.9.2.3 Management of Privileged Access Rights

Control- A.9.2.3 Management of Privileged Access Rights The allocation and usage of exclusive access privileges will be limited and controlled.

Implementation guidance- A structured authorizing procedure in accordance with the appropriate access management policies should monitor the allocation and usage of delegated access privileges.

Following steps should be taken into consideration:

  1. The privileges of access associated with each system or process, e.g. The operating system, the database management system and each application and the users to whom they need to be assigned should be identified;
  2. Preferential access privileges would be assigned to users on a need-to-use basis and on an event-to-event basis in accordance with the Access Management Policy, i.e. based on the necessary criteria for their functional roles.
  3. The authorization and the record of all assigned privileges should be maintained. Privileged access should not be issued until the authorization process has been completed;
  4. The conditions for the expiry of the privilege of access rights should be defined;
  5. The privilege of access rights should be assigned to a user ID different from those used for normal business activities. Regular business activities should not be carried out with a privileged ID;
  6. The competences of users with privileged access rights should be reviewed on a regular basis in order to verify that they comply with their duties;
  7. Specific procedures should be defined and maintained in order to prevent unauthorized use of generic user IDs according to system configuration capabilities,
  8. In the case of generic user IDs, the confidentiality of secret authentication information should be maintained when shared (e.g. changing passwords frequently and as soon as possible when a privileged user leaves or changes jobs, communicating them to privileged users with appropriate mechanisms).
Treat your password like your toothbrush, Don’t let anybody else use it and get a new one after every six months. -Clifford Stoll

Other Information- A significant contributor to failures and breaches of systems is the improper use of system administrator privileges (any information system function or facility that enables the user to bypass system or application control).

Related Product : ISO 27001 Lead Auditor Training And Certification ISMS

A.9.2.4 Management of Secret Authentication Information of Users

Control- A structured management process should control the allocation of secret authentication information.

Implementation Guidance- Following requirements should be included in the Process:

1) Users will sign a declaration to preserve sensitive personal secret authentication details and to hold mutual (that is, shared) sensitive authentication information strictly inside the group members; this signed agreement can be included in the terms and conditions of employment;

2) When users are required to maintain their own secret authentication information, secure secret authentication information should originally be provided to them that they must change for the first time;

3) Procedures for verifying the identity of the user should be established prior to the provision of new, replacement or temporary secret authentication information;

Also Read : ISO 27001 Annex : A.9.2 User Access Management

4) Temporary secret authentication information should be given to users in a safe manner; the use of third parties or insecure (clear text) e-mail messages should be avoided;

5) The details on temporary secret authentication should be unique and not guessable to a person;

6) Users will acknowledge receipt of information on secret authentication;

7) Upon activation of systems or applications, the default vendor secret authenticationdetails should be altered.

Other Information- Passwords are a common type of information for secret authentication and are a common way to verify the user’s identity. Other types of hidden authentication information are encryption keys and data stored on hardware tokens (e.g. smart cards).

Read More : https://www.info-savvy.com/iso-27001-annex-a-9-2-3-a-9-2-4/

---------------------------------------------------------------------------------------------------------------

Infosavvy, 2nd Floor, Sai Niketan, Chandavalkar Road Opp. Gora Gandhi Hotel, Above Jumbo King, beside Speakwell Institute, Borivali West, Mumbai, Maharashtra 400092

Contact us – www.info-savvy.com

https://g.co/kgs/ttqPpZ

要查看或添加评论,请登录

社区洞察

其他会员也浏览了