Find Resources & Connect with members on topics that interest you.

AI - Acquire and Implement

PO - Plan and Organize

DS - Deliver and Support

Please sign in to see your topics.

You must be logged in to join this group.

DS5.3 - Identity Management

This topic is intended to enable collaboration and sharing of information to facilitate a better understanding and approach to implementing this COBIT control objective based on the risk, value and guidance provided by its corresponding control practices.

COBIT Control Objective DS5.3 - Identity Management is contained within Process Popup Ensure Systems Security.

Learn more about COBIT and related publications.

Click “Join This Community” to be able to actively participate in discussions and contribute content. You must be an ISACA member to join this topic. Join ISACA now.

 
This Topic Has:
3 Members
0 Online
818 Visits

 Recent Discussions

Community Leader

Knowledge Center Manager

Knowledge Center Manager

Title: Become a Topic Leader!

Points: 3


Identity Management

Ensure that all users (internal, external and temporary) and their activity on IT systems (business application, IT environment, system operations, development and maintenance) are uniquely identifiable. Enable user identities via authentication mechanisms. Confirm that user access rights to systems and data are in line with defined and documented business needs and that job requirements are attached to user identities. Ensure that user access rights are requested by user management, approved by system owners and implemented by the security-responsible person. Maintain user identities and access rights in a central repository. Deploy cost-effective technical and procedural measures, and keep them current to establish user identification, implement authentication and enforce access rights.

View value and Risk Drivers  help

Hide value and Risk Drivers help


Value Drivers

  • Effective implementation of changes
  • Proper investigation of improper access activity
  • Secure communication ensuring approved business transactions
  Risk Drivers
  • Unauthorised changes to hardware and software
  • Access management failing business requirements and compromising the security of business-critical systems
  • Unspecified security requirements for all systems
  • Segregation-of-duty violations
  • Compromised system information

View Control Practices  help

Hide Control Practices  help

  1. Establish and communicate policies and procedures to uniquely identify, authenticate and authorise access mechanisms and access rights for all users on a need-to-know/need-to-have basis, based on predetermined and preapproved roles. Clearly state accountability of any user for any action on any of the systems and/or applications involved.
  2. Ensure that roles and access authorisation criteria for assigning user access rights take into account:
    • Sensitivity of information and applications involved (data classification)
    • Policies for information protection and dissemination (legal, regulatory, internal policies and contractual requirements)
    • Roles and responsibilities as defined within the enterprise
    • The need-to-have access rights associated with the function
    • Standard but individual user access profiles for common job roles in the organisation
    • Requirements to guarantee appropriate segregation of duties
  3. Establish a method for authenticating and authorising users to establish responsibility and enforce access rights in line with sensitivity of information and functional application requirements and infrastructure components, and in compliance with applicable laws, regulations, internal policies and contractual agreements.
  4. Define and implement a procedure for identifying new users and recording, approving and maintaining access rights. This needs to be requested by user management, approved by the system owner and implemented by the responsible security person.
  5. Ensure that a timely information flow is in place that reports changes in jobs (i.e., people in, people out, people change). Grant, revoke and adapt user access rights in co-ordination with human resources and user departments for users who are new, who have left the organisation, or who have changed roles or jobs.

 

Discussions: 0 total

Must be a Topic member to contribute

No Results Found

Documents & Publications: 76 total

Events & Online Learning: 13 total

7 May 2012
ISACA International Event
Orlando, Florida, USA
Get the knowledge you need to stay one step ahead of the competition and keep up with changing professional trends at ISACA’s North America CACS Conference.
14 May 2012
ISACA International Event
Chicago, IL, USA
15 May 2012
ISACA International Event
Washington, DC, USA
12 Jun 2012
ISACA International Event
Dallas, Texas, USA
ISACA Training is a unique educational event designed to provide the tools you need to maintain, update and upgrade your skills, and to continue your professional development.
7 Aug 2012
ISACA International Event
Chicago, Illinois, USA
ISACA Training is a unique educational event designed to provide the tools you need to maintain, update and upgrade your skills, and to continue your professional development.

Journal Articles: 260 total

Volume 3, 2012
by Steven J. Ross, CISA, CISSP, MBCP
To accelerate investments in security, we security professionals must do a better job of communicating the reality of the threats that our organizations face.
Volume 3, 2012
by Fabrizio Baiardi, Claudio Telmon, CISA, CISSP, and Daniele Sgandurra, Ph.D.
Haruspex is a risk evaluation methodology defined and implemented by the research group on risk management in the Department of Computer Science at the University of Pisa, Italy.
Volume 2, 2012
by Ed Gelbstein, Ph.D.
In the last couple of years, it has become evident that no organization can avoid being influenced by the tsunami of innovative technology, with ever shorter life cycles.
Volume 1, 2012
by Michael Mendelsohn, CISSP, Antoine Philipovitch, William Welch, CISM, and Robert Zanella, CISA
One of today’s big security marketing pushes is enterprise single sign-on (ESSO).
Volume 1, 2012
by Edward Amoroso | Reviewed by Jeimy J. Cano M., Ph.d., CFC, CFE, CMAS
This book is particularly interesting to and useful for information security and IT governance professionals because of its strategic and tactical guidance that can help refine decisions on the protection of critical infrastructure.
Volume 6, 2011
by Ed Gelbstein, Ph.D.
Information security has become a visible issue in business, on the move and at home.

Wikis: 2 total

Blog Posts: 26 total

On the AS/400 (System i) it is possible to audit for default passwords using the ANZDFTPWD command. A default password is defined as a password which is the same as the user profile. The command behaves slightly differently depending on the value of the s...
Posted By : Ian Cooke | 0 comments
The main idea I am trying to advocate with these posts is a simple one.  Compare a database you are auditing against a database that you know already meets the standards required by the organisation you are auditing. This is achieved by creating “CSV ty...
Posted By : Ian Cooke | 1 comments
We have covered most of the core items that should be consider when performing an Oracle database audit in previous posts, however there a number of other items that I would typically look into. Database Links A database link is an object in one database...
Posted By : Ian Cooke | 0 comments
The company you are auditing should have a policy on what is being audited within your Oracle database.  The level of auditing will almost certainly be affected by the sensitivity of the data. Good examples and bench marks for auditing may be seen in the...
Posted By : Ian Cooke | 0 comments
Typically application access to an Oracle database is via one of two methods.  Either all users access the same database using a single (proxy) user which is defined in an initialisation (.INI) file, registry etc. Or the users access the database individ...
Posted By : Ian Cooke | 1 comments
Before we get into auditing Oracle privileges a reminder of a few definitions might be helpful. A user privilege is the right to run a particular type of SQL statement, or the right to access an object belonging to another user, run a PL/SQL package, and...
Posted By : Ian Cooke | 1 comments