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.

AI2.5 - Configuration and Implementation of Acquired Application Software

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 AI2.5 - Configuration and Implementation of Acquired Application Software is contained within Process Popup Acquire and Maintain Application Software.

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
4443 Visits

 Recent Discussions

Community Leader

Knowledge Center Manager

Knowledge Center Manager

Title: Become a Topic Leader!

Badge: Energizer


Configuration and Implementation of Acquired Application Software

Configure and implement acquired application software to meet business objectives.

View value and Risk Drivers  help

Hide value and Risk Drivers help


Value Drivers

  • Acquired system configured to meet business-defined requirements
  • Acquired system compliant with existing architecture
  Risk Drivers
  • Loss of business focus
  • Inability to apply future updates effectively
  • Reduced system availability and integrity of information

View Control Practices  help

Hide Control Practices  help

  1. Assess the impact of any major upgrade and classify it according to agreed-upon objective criteria (such as business requirements), based on the outcome of analysis of the risk involved (such as impact on existing systems and processes or security), cost-benefit justification and other requirements. Follow normal system development and implementation processes as appropriate for the nature of the change.
  2. Consider interoperability with existing applications and databases, appropriate user interfaces, and efficient utilisation of technology resources (e.g., security framework and standards, availability, access management, auditability, networks and storage) in the design specification.
  3. Consider the impact of customisation and configuration on the performance and efficiency of the acquired packaged application software and on existing applications, operating systems and other infrastructure.
  4. Consider the effect of contractual terms with the vendor on the design of customisation and configuration.
  5. Consider the availability of source code for purchased/packaged applications in the customisation and configuration process. Review contractual arrangements with the vendor. Consider escrow arrangements where the source code is not available. Assess the risks in the event that the acquired application packaged software is no longer available at the expiry of a contract or for other reasons.
  6. Ensure that testing procedures cover verification of acquired application control objectives (such as functionality, interoperability with existing applications and infrastructure, system performance efficiency, integrated capacity and load stress testing, and data integrity).
  7. Conduct a design walk-through with IT and business stakeholders before customisation is initiated, as a part of the sign-off process for the customisation and configuration of application software specifications.
  8. Consider whether the implications of customisation and configuration require reassessment of strategies for acquired application packaged software.
  9. Obtain approval of business process owners for detailed design specifications for customisation and configuration of application software.
  10. Ensure that user and operational manuals (online help) are complete and updated where necessary to account for any customisation or special conditions unique to the implementation.
  11. Consider when the effect of cumulative customisations and configurations (including minor changes that were not subjected to formal design specifications) require a high-level reassessment of the acquired solution and associated functionality. Assess whether these changes trigger the development of a detailed design specification for customisation and configuration of the application software. Assess whether these changes restrict the ability of the organisation to adopt vendor upgrades to purchased applications packaged software.

Discussions: 0 total

Must be a Topic member to contribute

No Results Found

Documents & Publications: 69 total

Must be a Topic member to contribute
View All »
Downloads
Posted by ISACA 1426 days ago
Books
Posted by ISACA 505 days ago
Books
Posted by ISACA 719 days ago
Books
Posted by ISACA 824 days ago

Events & Online Learning: 15 total

Journal Articles: 236 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 1, 2018
by Aditya K. Sood, Ph.D., and Rehan Jalil
With the robust requirements listed by upcoming regulations, such as GDPR, the importance of a cloud app security solution cannot be ignored.
Volume 1, 2018
by Sandy Fadale, CRISC, CISM, CGEIT
Get to know your network.
Volume 6, 2017
by Robert Putrus, CISM, CFE, CMC, PE, PMP
This article presents a risk-based management approach to third-party data security risk and compliance through the development of a third-party risk register.
Volume 6, 2017
by Guy Pearce
The modern GRC landscape has a significant impact on how an enterprise-scale big data project would be undertaken today.

Wikis: 2 total

Blog Posts: 147 total

Have you experienced ransomware attack so far and, if yes, what did you do to resolve? I set up Twitter poll here: https://twitter.com/DPleskonjic/status/953608717399941120 It lasts for seven days. Thank you for taking part in the poll.
Posted By : Dragan Pleskonjic | 2 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
I predict that on 1 July 2018, I will be calmly eating a barbecue sandwich, talking with friends and possibly, I will burn a copy of the RFC2246: TLS version 1.0 standard for entertainment value.  Those will less effective Vendor, Network, Systems, Applic...
Posted By : Don Turnblade | 0 comments