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.

PO3.1 - Technological Direction Planning

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 PO3.1 - Technological Direction Planning is contained within Process Popup Determine Technological Direction

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:
4 Members
0 Online
716 Visits

 Recent Discussions

Community Leader

Knowledge Center Manager

Knowledge Center Manager

Title: Become a Topic Leader!

Points: 3


Technological Direction Planning

Analyse existing and emerging technologies, and plan which technological direction is appropriate to realise the IT strategy and the business systems architecture. Also identify in the plan which technologies have the potential to create business opportunities. The plan should address systems architecture, technological direction, migration strategies and contingency aspects of infrastructure components.

View value and Risk Drivers  help

Hide value and Risk Drivers help


Value Drivers

  • Improved leveraging of technology for business opportunities
  • Improved integration of infrastructure and applications via defined standards for technical direction
  • Improved use of resources and capabilities
  • Reduced costs for technological acquisitions through reduced platforms and incrementally managed investments
  Risk Drivers
  • Technological acquisitions inconsistent with strategic plans
  • IT infrastructure inappropriate for organisational requirements
  • Deviations from the approved technological direction
  • Increased costs due to unco-ordinated and unstructured acquisition plans

View Control Practices  help

Hide Control Practices  help

  1. Perform a strengths, weaknessess, opportunities and threats (SWOT) analysis of all current critical and significant IT assets on a regular basis.
  2. Follow up on market evolutions and relevant emerging technologies.
  3. Identify the latest developments in IT that could have an impact on the success of the business.
  4. Establish the appropriate technological risk appetite (e.g., pioneer, leader, early adopter, follower).
  5. Identify what is needed in terms of technological directions for business systems architecture, migration strategies and contingency aspects of infrastructure components.

 

Discussions: 0 total

Must be a Topic member to contribute

No Results Found

Documents & Publications: 138 total

Must be a Topic member to contribute
View All »
Downloads
Posted by ISACA 344 days ago
Downloads
Posted by ISACA 397 days ago
Downloads
Posted by ISACA 397 days ago
Downloads
Posted by ISACA 729 days ago
Research
Posted by ISACA 17 hours ago
Books
Posted by ISACA 11 days ago

Events & Online Learning: 9 total

7 May 2012
ISACA International Event
Orlando, Florida, USA
Get the knowledge you need to stay one step ahead of the competition and keep up with changing professional trends at ISACA’s North America CACS Conference.
12 Jun 2012
ISACA International Event
Dallas, Texas, USA
ISACA Training is a unique educational event designed to provide the tools you need to maintain, update and upgrade your skills, and to continue your professional development.
7 Aug 2012
ISACA International Event
Chicago, Illinois, USA
ISACA Training is a unique educational event designed to provide the tools you need to maintain, update and upgrade your skills, and to continue your professional development.
10 Sep 2012
ISACA International Event
Munich, Germany
EuroCACS/ISRM is a multidimensional event featuring audit, security, governance and risk content, and the audit and security programs, tools and the resources you need to be responsive to industry changes.
11 Sep 2012
ISACA International Event
San Francisco, California, USA
ISACA Training is a unique educational event designed to provide the tools you need to maintain, update and upgrade your skills, and to continue your professional development.

Journal Articles: 347 total

Volume 3, 2012
by Kai-Uwe Ruhse, CISA, PCI QSA, and Maria Baturova
This article describes real cloud computing project case studies, which show that moving to the cloud is an important strategic decision for IT managers.
Volume 3, 2012
by Steve Markey
Once thought of as a technology solely for academia, non-RDBMS are now reaching critical mass in industry.
Volume 2, 2012
by Jonathan Trull, CISA, CFE, OSCP
Successful penetration of any critical resource could identify vulnerabilities that could become targets for real hackers.
Volume 2, 2012
by Charles Gold
While open-source technology offers significant benefits, using open-source components carries technical and business risks that cannot be ignored.
Volume 1, 2012
by Ronke Oyemade, CISA, CRISC, PMP
This article defines IT governance, addresses its importance, and describes how to apply the three lines of defense by implementing a combination of the Risk IT and COBIT frameworks.
Volume 1, 2012
by Prakhar Srivastava and Tarun Verma
Log management can play a pivotal role in addressing PCI DSS requirements, be a success factor and enabler for safeguarding cardholder transaction data, and provide a secure and vulnerability-free environment for cardholders.

Wikis: 2 total

Blog Posts: 31 total

On the AS/400 (System i) it is possible to audit for default passwords using the ANZDFTPWD command. A default password is defined as a password which is the same as the user profile. The command behaves slightly differently depending on the value of the s...
Posted By : Ian Cooke | 0 comments
The main idea I am trying to advocate with these posts is a simple one.  Compare a database you are auditing against a database that you know already meets the standards required by the organisation you are auditing. This is achieved by creating “CSV ty...
Posted By : Ian Cooke | 1 comments
We have covered most of the core items that should be consider when performing an Oracle database audit in previous posts, however there a number of other items that I would typically look into. Database Links A database link is an object in one database...
Posted By : Ian Cooke | 0 comments
The company you are auditing should have a policy on what is being audited within your Oracle database.  The level of auditing will almost certainly be affected by the sensitivity of the data. Good examples and bench marks for auditing may be seen in the...
Posted By : Ian Cooke | 0 comments
Typically application access to an Oracle database is via one of two methods.  Either all users access the same database using a single (proxy) user which is defined in an initialisation (.INI) file, registry etc. Or the users access the database individ...
Posted By : Ian Cooke | 1 comments
Before we get into auditing Oracle privileges a reminder of a few definitions might be helpful. A user privilege is the right to run a particular type of SQL statement, or the right to access an object belonging to another user, run a PL/SQL package, and...
Posted By : Ian Cooke | 1 comments