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.

AI3.3 - Infrastructure Maintenance

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 AI3.3 - Infrastructure Maintenance is contained within Process Popup Acquire and Maintain Technology Infrastructure.

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:
16 Members
0 Online
4589 Visits

 Recent Discussions

Community Leader

Knowledge Center Manager

Knowledge Center Manager

Title: Become a Topic Leader!

Badge: Energizer

Infrastructure Maintenance

Develop a strategy and plan for infrastructure maintenance, and ensure that changes are controlled in line with the organisation’s change management procedure. Include periodic reviews against business needs, patch management, upgrade strategies, risks, vulnerabilities assessment and security requirements.

View value and Risk Drivers  help

Hide value and Risk Drivers help

Value Drivers

  • Monitored maintenance contracts
  • Effective maintenance processes
  • Operational change management for replacement of software
  Risk Drivers
  • Disruptions in production processing
  • Unauthorised access to sensitive software
  • Technology failing to support business needs
  • Violation of licence agreements

View Control Practices  help

Hide Control Practices  help

  1. Establish a strategy and plan for infrastructure maintenance to provide overall guidance in line with the organisation’s change management procedures.
  2. Ensure that maintenance of the installed system software (patches, service packs and other updates) is managed through the established change management process and is performed in accordance with vendor procedures and guidelines by qualified and authorised internal and/or vendor personnel.
  3. Maintain documentation of system software, and ensure that it is complete and current. Require vendors to deliver new and updated documentation each time the system software is maintained.
  4. Maintain currency of system software by applying vendor upgrades or patches in a timely manner.
  5. Review on a regular basis the amount of maintenance being performed and the vulnerability to unsupported infrastructure; consider future risks, including security vulnerabilities. Report any issues identified for consideration within the infrastructure planning process.

Discussions: 0 total

Must be a Topic member to contribute

No Results Found

Documents & Publications: 79 total

Must be a Topic member to contribute
View All »
Posted by FarmService 1563 days ago
Posted by ISACA 1573 days ago
Posted by FarmService 2648 days ago
Posted by ISACA 652 days ago
Posted by ISACA 866 days ago

Events & Online Learning: 10 total

Journal Articles: 276 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 4, 2018
by Robert E. Davis, DBA, CISA, CICA
How organizational representatives communicate about technological innovation is often a significant factor in the success or failure of innovation management.
Volume 4, 2018
by Ian Cooke, CISA, CRISC, CGEIT, COBIT Assessor and Implementer, CFE, CPTE, DipFM, ITIL Foundation, Six Sigma Green Belt
Enterprises have many stakeholders, and “creating value” means different—and sometimes conflicting—things to each of them
Volume 4, 2018
by Guy Pearce, CGEIT
The IT Portfolio Management Model was based on the principles of financial portfolio management, specifically, the relationship between investment risk and investment return as per the so-called risk-return tradeoff.
Volume 4, 2018
Our organization is considering multiple projects for developing and implementing IT-based solutions. I have checked on various websites, but could not get a detailed list of generic risk scenarios for IT-related projects.

Wikis: 2 total

Blog Posts: 173 total

17 Jun 2018
We are happy to announce that  on Feb//2018  the ISACA awareness session  was held in Baghdad.This the first time to speak about ISACA Value in Iraq.Professional from government and private sector were excited to hear about ISACA value and they started to...
Posted By : Ali099 | 2 comments
Posted By : TafadzwaPadare | 1 comments
Hello and welcome to my first post of my new blog, 'Cybersecurity ROCKS!'.   As a long time member of the security community and new to the Vancouver area, I'd like to tell you a little about myself, how my career began and where my current passions in cy...
Posted By : cybersecgal | 1 comments
5 Jun 2018
Recently, I witnessed an interesting webcast by Scopism, an UK-based consulting and training company. They announced the publication of the SIAM(c) Foundation Body of Knowledge, available for free through their website Service Integration...
Posted By : Peter873 | 2 comments
Security in IoT environment
Posted By : Hyun239 | 0 comments
20 Apr 2018
Good day. I have an interesting situation that came about just this week.  New career opportunities are not all that they seem to be.  What I thought was going to be a great career change ended up in disaster.  With only one week and two day's, I was dism...
Posted By : Brian824 | 0 comments