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.

DS9.3 - Configuration Integrity Review

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 DS9.3 - Configuration Integrity Review is contained within Process Popup Manage the Configuration.

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:
6 Members
0 Online
2386 Visits

 Recent Discussions

Community Leader

Knowledge Center Manager

Knowledge Center Manager

Title: Become a Topic Leader!


Configuration Integrity Review

Periodically review the configuration data to verify and confirm the integrity of the current and historical configuration. Periodically review installed software against the policy for software usage to identify personal or unlicensed software or any software instances in excess of current license agreements. Report, act on and correct errors and deviations.

View value and Risk Drivers  help

Hide value and Risk Drivers help


Value Drivers

  • Identification of deviations from the baseline
  • Enhanced identification and solving of problems
  • Identification of unauthorised software
  Risk Drivers
  • Failure to identify business-critical components
  • Uncontrolled change management, causing business disruptions
  • Misused assets
  • Increased costs for problem solving

View Control Practices  help

Hide Control Practices  help

  1. To validate the integrity of configuration data, implement a process to ensure that configuration items are monitored. Compare recorded data against actual physical existence, and ensure that errors and deviations are reported and corrected.
  2. Using automated discovery tools where appropriate, reconcile actual installed software and hardware periodically against the configuration database, licence records and physical tags.
  3. Periodically review against the policy for software usage the existence of any software in violation or in excess of current policies and licence agreements. Report deviations for correction.

Discussions: 0 total

Must be a Topic member to contribute

No Results Found

Documents & Publications: 41 total

Must be a Topic member to contribute
View All »
Books
Posted by ISACA 130 days ago
Books
Posted by ISACA 136 days ago
Books
Posted by ISACA 310 days ago
Books
International Financial Reporting Standards have been mandatory in the EU since 2005 and are rapidly being adopted by countries throughout the world.
Posted by ISACA 320 days ago

Events & Online Learning: 0 total

No Results Found

Journal Articles: 42 total

Volume 3, 2013
by Larry G. Wlosinski, CISA, CISM, CRISC, CAP, CDP, CISSP, ITIL
How will an organization’s information security staff be affected if the organization’s computer systems are moved to a cloud environment?
Volume 2, 2013
by Nurudeen Odeshina, CISA, CISM, CRISC, ISO 27001 LI, ITSM
As is often said, “information security is not a destination, it is a journey,” and for the organization it means continuous improvement.
Volume 1, 2013
by Rajesh Bhatia, CISA, CGEIT, PMP, MDP
IT governance implementation and institutionalization in enterprise business units is dependent on buy-in from the business-unit executives.
Volume 1, 2013
by Ingrid Robinson, CPA, CIA, and Margaret Jodha, CPA, CGA
Today’s IT business environment requires regulatory compliance, cost control, availability, risk management, business alignment, timely project delivery, change and continuous innovation to deliver stakeholder value.
Volume 4, 2011
by Charu Pelnekar, CISA, CISM, ACA, AICWA, BCOM, CISSP, CPA, MCSE, QSA
The goal of this article is to provide guidance on the planning and decision-making processes associated with ISO 27001 implementation.
Volume 4, 2011
by Gan Subramaniam, CISA, CISM, CCNA, CCSA, CIA, CISSP, ISO 27001 LA, SSCP
Let us try to develop a checklist to audit the IT systems integration project.

Wikis: 2 total

Blog Posts: 8 total

DISCLAIMER :- Below information is just for knowledge sharing purpose and reference. Personally or on behalf of any organization; I do not recommend any specific / particular tool listed below. These are the ones which I have come across. there may be t...
Posted By : prathameshkarekar | 0 comments
Es importantísimo reconocer que la banca móvil y pagos móviles han llegado para quedarse y que aquellos bancos que no se ocupen ahora en prepararse tendrán grandes problemas en el largo plazo y esta es una opinión compartida con el equipo de BITS (Financi...
Posted By : Diego San Esteban | 0 comments
20 Jun 2012
The increased complexity and diversity in the information systems and the inability to rebuild the information systems from scratch is forcing enterprises to look at EAI as an alternative solution that will help extend the life of the existing application...
Posted By : Kannan | 0 comments
7 Mar 2012
To share various espects in cloud computing viz; history, availability, deployment, integrity, availability, confidentiality, security, cloud sharing etc.
Posted By : MoizB583519 | 2 comments
APT Defense Strategy   By Kevin J. Murphy, CISSP, CISM, CGEIT September 30, 2010 WHAT IS APT? APT is an acronym for Advance Persistent Threat.  Isn’t that descriptive?  In reality there is a lot behind the APT which might not be that obvious from u...
Posted By : Kevin J. Murphy | 1 comments
12 May 2011
ITGA Blog focused IT Governance & IT Architecture Experiences.Here, you will can to learn more about theses topics. Regards,Roberto ArteiroITGA Editor.
Posted By : Roberto Arteiro | 1 comments