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:
3 Members
1 Online
2460 Visits

 Recent Discussions

Community Leader

Knowledge Center Manager

Knowledge Center Manager

Title: Become a Topic Leader!


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: 101 total

Must be a Topic member to contribute
View All »
Downloads
Posted by ISACA 216 days ago
Downloads
Posted by ISACA 1091 days ago
Books
Posted by ISACA 130 days ago
Exam Preparation
Posted by ISACA 130 days ago

Events & Online Learning: 7 total

10 Jun 2013
ISACA International Event
Berlin, Germany
Early bird deadline has been extended: save over US $350 when you register by 1 May. Learn from industry-leading IT experts at Insights 2013. This is a unique opportunity to discover revolutionary new ideas at the world’s premier business event.
16 Sep 2013
ISACA International Event
London, England
Stay on top of the trends and opportunities of the dynamic technology industry at EuroCACS/ISRM 2013 in Berlin—the leading European conference for IT audit, assurance, security and risk professionals. Save over US $200 when you register by 22 July!
30 Sep 2013
ISACA International Event
Medellín, Colombia
La Conferencia Latinoamericana CACS/ISRM 2013 en Medellín, Colombia es la conferencia principal latinoamericana para los profesionales de auditoría, riesgo y seguridad de la información. Ahorre más de EE.UU. $ 100 si se inscribe antes del 7 de agosto!
14 Oct 2013
ISACA International Event
Boston, MA, USA

Journal Articles: 240 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 3, 2013
by Steven DeFino and Larry Greenblatt | Reviewed by Dauda Sule, CISA
This Guide is targeted toward individuals who wish to attain the Certified Ethical Hacker (CEH) certification.
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 2, 2013
by Darlene Tester
Not performing a full risk assessment before determining what security controls should be implemented is equivalent to not “looking before you leap.”
Volume 2, 2013
by Bob Smart, CISA, CISM, CRISC, MACS Snr, MBIS
Professional certifications can be defined as a promise made by the certifying body that the recipient has demonstrated a minimum level of capabilities.
Volume 2, 2013
by Samuel Pierre-Louis, CISSP-ISMP, René Sanchez, CISM, CBCP, MBCI, and Molly Shek, CISM, CGEIT, CRISC, PMP, RHIA
How does an organization that is faced with numerous federal and state compliance requirements meet the challenge?

Wikis: 2 total

Blog Posts: 129 total

A recent publication in a local newspaper, indicated that an employee was charged with fraud with regards to claims of insurance payments that were lodged with the company were paid out to people who were not entitled to receive such payments. What po...
Posted By : Paulina.PNI | 1 comments
Check out the video interview with Jack Danahy on the 2013 Global Reputational Risk and IT Study and please leaving your ratings and feedback on the video landing page. https://ibm.biz/Bdxb3k
Posted By : Calvin Powers | 0 comments
Grupos de Estudio para Acreditaciones de JUNIO, SEPTIEMBRE Y DICIEMBRE 2013. Para los que esten interesados en la presentación del exámen de certificación CISA y CISM  o para cualquiera que desee comenzar a prepararse para estas o las próximas pruebas, pu...
Posted By : Alexander Osorio | 0 comments
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
22 Feb 2013
It is disheartening in the extreme when privacy, security, audit, governance and legal professionals persist the self-fulfilling-prophetic chant that “privacy is dead.” It isn't dead—or even dying. Quite the opposite, in fact. Seven bills have come b...
Posted By : WLWells | 1 comments
If I were to tell you that the following capture was off a WiFi Access Point - you may be alarmed. If however, I was also to tell you this was an AP supporting the WiFi access needs for the Clients of a very well known 4 Star London Hotel, you may be even...
Posted By : John379 | 0 comments