ISACA ITAF (Performance Standards/Guidelines) Flashcards
Standards: Risk Assessment in Planning (1201)
- 1) The IT audit and assurance function shall use an appropriate risk assessment approach (i.e., data-driven with both quantitative and qualitative factors) and supporting methodology to develop the overall IT audit plan and determine priorities for the effective allocation of IT audit resources.
- 2) IT audit and assurance practitioners shall identify and assess risk relevant to the area under review when planning individual engagements.
- 3) IT audit and assurance practitioners shall consider subject matter risk, audit risk and related exposure to the enterprise when planning audit engagements.
Guidelines: Risk Assessment in Planning (1201) - What is the goal of risk assessment?
The goal of risk assessment is to identify the parts of an activity that should receive more audit focus and to reduce the risk of reaching an incorrect conclusion.
AT MINIMUM, the risk assessment should include an analysis of risk related to:
(1) System availability
(2) Data integrity
(3) Business information confidentiality
Guidelines: Risk Assessment in Planning (1201) - What are the outcomes of performing a risk assessment?
- Auditors develop an IT audit schedule (framework for the IT audit activities) as a result of risk assessment/
- Risk assessments are used to quantify and justify the amount of IT audit resources needed to complete the IT audit plan and to meet the requirements for the audit engagement.
- Used to inform the auditor’s decisions in what areas/business functions should be audited, the amount of time/resources to be allocated to the audit, and the nature/timing/extent of audit procedures.
- May also help identify which areas/items of interest may warrant Continuous Monitoring by management and Continuous Auditing by practitioners.
- Helps auditors develop an audit plan that considers both non-IT and IT audit and assurance requirements/activities, as well as addresses the responsibilities set by the audit charter.
Guidelines: Risk Assessment in Planning (1201) - What must an auditor consider when selecting the most appropriate risk assessment methodology?
To determine the most appropriate risk assessment methodology, practitioners should consider:
Type of information required to be collected. Some systems use financial effects as the only measure, which is not always appropriate for IT audit engagements.
Cost of software or other licenses required to use the methodology
Extent to which the information required is already available
Amount of additional information required to be collected before reliable output can be obtained, and the cost of collecting the information (including the required time investment in the collection exercise)
Opinions of other users of the methodology, and their views of how well it has assisted them in improving the efficiency and/or effectiveness of their audits
Willingness of those charged with governance of the IT audit area to accept the methodology as the means of determining the type and level of audit work carried out
Guidelines: Risk Assessment in Planning (1201) -
Auditors should recognize that the ____ the materiality threshold is, the ____ precise the audit expectations will be, and the ____ the audit risk.
Auditors should recognize that the lower the materiality threshold is, the more precise the audit expectations will be, and the greater the audit risk.
Guidelines: Risk Assessment in Planning (1201) - To gain additional assurance in instances of high audit risk/low materiality threshold, what must an auditor do?
To gain additional assurance in instances of high audit risk or lower materiality threshold, practitioners should compensate either by (1) extending the scope or nature of the IT audit tests or by (2) increasing or extending the substantive testing.
Guidelines: Risk Assessment in Planning (1201) - Auditors should assess the Control Risk as high unless what is present?
Auditors should assess the control risk as high unless relevant internal controls are:
(1) identified
(2) validated via testing (i.e. comparison of performance to design) and proved to be operating effectively
Guidelines: Risk Assessment in Planning (1201) - Pervasive IT Controls vs. Detailed IT Controls vs. General Controls
(1) Pervasive IT Controls: Considered a subset of general controls; they are the general controls that focus on the management and monitoring of the IT environment. They affect all IT-related activities. They affect the reliability of Application Controls (controls in the business process systems) and Detailed IT Controls. Affects ALL IS-related activities.
Weak Pervasive IT Controls should alert auditors to the possibility of a high risk that the controls designed to operate at a detailed level may be ineffective.
(2) Detailed IT Controls: Comprised of Application Controls + General Controls not included in Pervasive IT Controls. These are controls over the acquisition, implementation, delivery, and support of IS systems and services and relate to the governance and management of information and technology.
(3) General Computer Control (“General Controls”): Controls other than Application Controls that relate to the environment within which computer-based application systems are developed, maintained, and operated and therefore all applicable to ALL applications.
The objective of General Controls are to (1) ensure the proper development and implementation of applications, (2) ensure the integrity of program and data files, and (3) ensure integrity of computer operations.
Examples: Implementation of an IS strategy, IS security policy, the organization of IS staff to separate conflicting duties, planning for disaster prevention and recovery (DRP).
Guidelines: Risk Assessment in Planning (1201) - In determining the level of substantive testing required, what should auditors consider?
In determining the level of substantive testing required, practitioners should consider:
Assessment of inherent risk
Conclusions on control risk following compliance testing
(The higher the assessment of inherent and control risk, the more audit evidence auditors normally should obtain from the performance of substantive audit procedures.)
Standards: Audit Scheduling (1202)
- 1) The IT audit and assurance function shall establish an overall strategic plan resulting in short-term and long-term audit schedules. Short-term planning consists of audits to be performed within the year, while long-term planning is comprised of audits based on risk-related matters within the enterprise’s information and technology (I&T) environment that may be performed in the future.
- 2) Both short-term and long-term audit schedules should be agreed upon with those charged with governance and oversight (e.g., audit committee) and communicated within the enterprise.
- 3) The IT audit and assurance function shall modify its short-term and/or long-term audit schedules to be responsive to organizational needs (i.e., unexpected events or unplanned initiatives). Any audit displaced to accommodate an audit of an unexpected event or unplanned initiative should be reassigned to a future period.
Standards: Audit Planning (1203)
1203.1) IT audit and assurance practitioners shall plan each IT audit and assurance engagement to address the nature, timing and extent of audit procedures to be performed. The plan should include:
Areas to be audited
Objectives
Scope
Resources (e.g., staff, tools and budget) and schedule dates
Timeline and deliverables
Compliance with applicable laws/regulations and professional auditing standards
Use of a risk-based approach for engagements that are not related to legal or regulatory compliance
Engagement-specific issues
Documentation and reporting requirements
Use of relevant technology and data analysis techniques
Consideration of the cost of the engagement relative to the potential benefits
Communication and escalation protocols for situations that may arise during the performance of an IT audit engagement (e.g., scope limitations or unavailability of key personnel)
During fieldwork, it may become necessary to modify audit procedures created during planning as the engagement progresses.
1203.2 IT audit and assurance practitioners shall develop and document an IT audit and assurance engagement program (AUDIT PROGRAM) that describes the step-by-step procedures and instructions to be used to complete the audit.
Guidelines: Audit Planning (1203)
Auditor assessment of materiality.
During the planning process, practitioners should establish levels of planning materiality such that the audit work will be sufficient to meet the audit objectives and will use audit resources efficiently.
For example, in the review of an existing system, practitioners should evaluate materiality of the various components of the system in planning the audit engagement for the work to be performed. Both qualitative and quantitative aspects should be considered in determining materiality.
Definition - Materiality: An auditing concept regarding the importance of an item of information with regard to its impact or effect on the functioning of the entity being audited. An expression of the relative significance or importance of a particular matter in the context of the enterprise as a whole.
Risk assessments help provide reasonable assurance that all material items will be adequately covered during the engagement. Audit strategies, materiality levels, and resource requirements can then be developed.
Guidelines: Performance and Supervision (1204)
Communication of Findings to Auditee
After documenting work performed and identifying findings, the next step is performed:
Confirming findings and following up on corrective actions: Practitioners should confirm their findings with the auditee. Should the auditee perform corrective actions on the findings before the end of the audit engagement, practitioners should include the actions taken in the documentation (and conclusion) but also mention the original findings.
Referred to as “Clearing the findings”
Only then are conclusions drawn and the reporting process is initiated.
Guidelines: Performance and Supervision (1204)
What factors are used to assess evidence “reliability”?
Practitioners should consider reliability of audit evidence (i.e., (1) independence of the provider of the evidence, (2) qualifications of the provider of the information, (3) objectivity of the evidence, and (4) timing of the evidence).
Guidelines: Performance and Supervision (1204)
What should the auditor do when deviations from expectations are identified during testing?
If deviations from expectations are identified, practitioners should ask management about the reasons for the differences.
If management’s explanations are adequate, based on practitioners’ professional judgment, practitioners should modify their expectations and reanalyze the evidence and information.
Significant deviations the auditee does not adequately explain should result in audit findings and be communicated to executive management or those charged with governance and oversight of the audit function.
Depending on the circumstances, practitioners may recommend appropriate actions to take (sometimes referred to as “quality improvement program”).