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.

PO9.3 - Event Identification

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 PO9.3 - Event Identification is contained within Process Popup Assess and Manage IT Risks.

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:
9 Members
0 Online
4094 Visits

 Recent Discussions

Community Leader

Knowledge Center Manager

Knowledge Center Manager

Title: Become a Topic Leader!

Badge: Energizer

Event Identification

Identify events (an important realistic threat that exploits a significant applicable vulnerability) with a potential negative impact on the goals or operations of the enterprise, including business, regulatory, legal, technology, trading partner, human resources and operational aspects. Determine the nature of the impact and maintain this information. Record and maintain relevant risks in a risk registry.

View value and Risk Drivers  help

Hide value and Risk Drivers help

Value Drivers

  • Consistent approach to risk event identification
  • Focus on significant risk events
  Risk Drivers
  • Irrelevant risk events identified and focused on whilst more important events are missed

View Control Practices  help

Hide Control Practices  help

  1. Obtain agreement and sign-off from stakeholders of key events and their impacts.
  2. Identify potential events that could negatively affect enterprise goals or operations considering results of former audits, inspections and identified incidents, using checklists, workshops, process flow analysis, or other tools and techniques.
  3. Identify potential negative impacts that are relevant and significant for the enterprise for each of the selected events. Record and maintain the information in the risk registry, using the enterprise risk management framework terminology.
  4. Involve appropriate cross-functional teams in the event and impact identification activity. Depending on the scope of the assessment, these teams may be composed of representatives from the IT, risk management and business functions.
  5. Review all potential events as a whole to ensure completeness and to identify interdependencies that could affect impact and probability.

Discussions: 0 total

Must be a Topic member to contribute

No Results Found

Documents & Publications: 91 total

Must be a Topic member to contribute
View All »
Posted by ISACA 1447 days ago
Posted by ISACA 740 days ago
Posted by ISACA 845 days ago
Posted by ISACA 855 days ago

Events & Online Learning: 13 total

Journal Articles: 305 total

Volume 3, 2107
by Jayakumar Sundaram, CISA, ISO 27001 LA
The SoA is a continuously updated and controlled document that provides an overview of information security implementation.
Volume 6, 2106
by Venkatasubramanian Ramakrishnan, CISM, CRISC, CHFI
Bayesian networks can capture the complex interdependencies among risk factors and can effectively combine data with expert judgment.
Volume 2, 2018
by Ofir Eitan, CISM, CCSK, CTI
In the wake of the Target breach, the threat of cyberattacks using an enterprise’s supply chain as a delivery vector has become a common concern within the information security community.
Volume 2, 2018
by Indrajit Atluri, CRISC, CISM, CISSP, HCISPP, ITILv3
Cyber insurance, along with cyberrisk, has become a very common agenda item on the boardroom discussion list in recent times.
Volume 2, 2018
by Steven J. Ross, CISA, CISSP, MBCP
In this era of multi-modal technology, many disaster recovery issues are solved, some are simply transferred and a few are made worse.
Volume 2, 2018
by Rassoul Ghaznavi-Zadeh, CISM, COBIT Foundation, SABSA SCF, TOGAF 9
A top-down approach to enterprise security architecture can be used to build a business-driven security architecture.

Wikis: 2 total

Blog Posts: 154 total

La Tecnología de la Información (TI), en todas sus áreas (base de datos, seguridad de la información, desarrollo de software, redes, etc.), debe tener como objetivo primario el apoyo a los Procesos del Negocio (PN) de la organización. Sin embargo, es comú...
Posted By : emorro | 0 comments
Have you experienced ransomware attack so far and, if yes, what did you do to resolve? I set up Twitter poll here: It lasts for seven days. Thank you for taking part in the poll.
Posted By : Dragan Pleskonjic | 5 comments
Bitcoin Trade a Bubble! Block Chain Technology Useful .ISACA Members whats your Take on Bitcoin Trade, Is its a bubble that wont last long.Block chain Technology is useful and its continuously growing to as form of secure record  management and secured us...
Posted By : MUGAMBI865 | 1 comments
There is no doubt with our current business environment, we will be experiencing more cyber breaches in the next few months.  The latest threat is an architectural design flaw in newer CPU's.  These design vulnerabilities could allow attackers to intercep...
Posted By : Fred586 | 1 comments
There are some math models for business that MBAs are taught. Just like assembling burgers for fast food or call wait queue management in a call center, vulnerability patching is a time based business opportunity. Leadership can be expected to use this ...
Posted By : Don Turnblade | 1 comments
My personal thoughts after listening to C-level executives at the CxO Roundtable Series sponsored by Intel, IBM, HyTrust & ReedSmith. For an invite, please reach out to me. Data Protection under the GDPR For past few months, I’ve been helping to org...
Posted By : Thomas152 | 1 comments