Study guide

3.2 Applying Topical Requirements When Planning

CIA Part 2 Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: CIA Part 2 Exam Orientation

1.1 Current CIA Part 2 Exam Facts 1.2 Eligibility, Fees, and Pearson VUE Scheduling 1.3 Scoring, Results Timing, and the 2025 Syllabus Map

2 Chapter 2: Engagement Objectives and Scope

2.1 Topical Requirements in Objectives and Scope 2.2 Elements Used to Build Engagement Objectives 2.3 Scope Limitations, Stakeholder Requests, and Scope Changes

3 Chapter 3: Evaluation Criteria and Planning Context

3.1 Selecting and Testing Evaluation Criteria 3.2 Applying Topical Requirements When Planning 3.3 Strategy, Risk Management, and Performance of the Activity Under Review

4 Chapter 4: Technology, Continuity, and Finance in Planning

4.1 Cybersecurity, IT General Controls, Privacy, and Data Security 4.2 Business Continuity, Disaster Recovery, and Resilience 4.3 Finance and Accounting Concepts for the Activity Under Review

5 Chapter 5: Business Process and System Risks in Planning

5.1 Asset, Supply Chain, Inventory, Payables, Procurement, and Compliance Processes 5.2 Third-Party Process Risks 5.3 CRM, ERP, and GRC System Risks

6 Chapter 6: Engagement Approach and Project Management

6.1 Agile, Traditional, Integrated, and Remote Approaches 6.2 Project Management While Planning and Conducting Engagements

7 Chapter 7: Engagement Risk Assessment

7.1 Topical Requirements and Pervasive Financial, Operational, IT, Cyber, and Regulatory Risks 7.2 Emerging Risks and the Impact of Change 7.3 Methods to Evaluate and Prioritize Risks and Controls

8 Chapter 8: Structure, Environment, and Culture

8.1 Centralized vs Decentralized, Flat vs Traditional, In-Person vs Remote 8.2 Culture, Group Behavior, and Tone at the Top

9 Chapter 9: Control Design, Effectiveness, and Efficiency Procedures

9.1 Procedures to Evaluate Control Design 9.2 Procedures to Test Operating Effectiveness 9.3 Procedures to Test Control Efficiency

10 Chapter 10: Work Programs, Testing Methodologies, and Resources

10.1 Evaluating Adequacy of the Engagement Work Program 10.2 Testing Methodologies for Accounting, Finance, IT, Operations, and Cybersecurity 10.3 Financial, Human, and Technological Resources and Limitation Implications

11 Chapter 11: Information Sources and Preliminary Survey

11.1 Interviews, Observations, and Walk-Throughs 11.2 Data Analysis as an Information Source 11.3 Policies, Checklists, Risk-and-Control Questionnaires, and Self-Assessments

12 Chapter 12: Evidence Relevance, Sufficiency, and Reliability

12.1 Criteria for Evidence Quality 12.2 Independence, Corroboration, and the Control Environment 12.3 Evidence an Informed, Competent Person Could Rely On

13 Chapter 13: Technology Options for Findings and Conclusions

13.1 Artificial Intelligence, Machine Learning, and Robotic Process Automation 13.2 Continuous Monitoring, Dashboards, and Embedded Audit Modules

14 Chapter 14: Process Mapping and Data Analytics

14.1 Workflow Segments, Process Maps, Walk-Throughs, and RACI 14.2 Structured vs Unstructured Data and the Analytics Process 14.3 Diagnostic, Prescriptive, Predictive, Anomaly, and Text Analysis

15 Chapter 15: Analytical Review and Finding Evaluation

15.1 Ratios, Variances, Trends, and Benchmarking 15.2 Selecting Analytical Techniques for Engagement Objectives 15.3 Comparing Existing Conditions to Evaluation Criteria 15.4 Root Causes, Effects, and Significance of Findings

16 Chapter 16: Workpapers and Engagement Conclusions

16.1 Organizing Complete Workpapers with Sufficient Evidence 16.2 Linking Workpapers to Results; Retention, Regulation, and Policy 16.3 Aggregating Findings and Concluding on Governance, Risk, and Control

17 Chapter 17: Engagement Supervision

17.1 Supervision Throughout Planning and Fieldwork 17.2 Coordinating Assignments and Reviewing Workpapers and Conclusions 17.3 Evaluating Auditors' Performance

18 Chapter 18: Communication During the Engagement

18.1 Formal and Informal Communication Across Planning, Fieldwork, and Reporting 18.2 Situations That Require Escalation 18.3 Selecting Appropriate Stakeholders for Engagement Communication

19 Chapter 19: Final Review and Test Day

19.1 2025 vs 2019 Traps and Part 2 vs Part 3 Boundaries 19.2 Pacing, Test-Center Rules, and Official Results

3.2 Applying Topical Requirements When Planning

Key Takeaways Explain This Topic AI

Topical Requirements are a mandatory IPPF component for assurance when the topic is in scope; Global Guidance (GTAGs, Global Practice Guides, user guides) is recommended, not mandatory

The Cybersecurity Topical Requirement was issued 5 February 2025 and became effective 5 February 2026; it is a minimum baseline across governance, risk management, and control processes — not a substitute for NIST or a CISSP body of knowledge

Applicability triggers: the topic is the subject of an engagement in the internal audit plan, is identified while performing an engagement, or is the subject of an engagement request not on the original plan

Planning implications are the required risk/control considerations, the evidence you will need, the specialists you may need, and how the baseline fits objectives and scope already set

Evidence that each requirement was assessed for applicability must be retained; exclusions need a documented rationale; conformance is evaluated in quality assessments and the CAE remains responsible if specialist work is outsourced

Last updated: August 2026

3.2 Applying Topical Requirements When Planning

Quick Answer: When a published Topical Requirement's topic is in assurance scope, you must apply it in conformance with the Global Internal Audit Standards. Planning is where you translate that mandate into required risk and control considerations , the evidence the work program will collect, the specialists you may need, and a documented decision about which requirements apply to objectives already set. Global Guidance is recommended. Topical Requirements are not.

Chapter 2 covered Topical Requirements when setting objectives and scope. This section is CIA Part 2 A3a : recognize how to apply them when planning the engagement — staffing, procedures, evidence, and the fit to objectives that already exist. Do not rebuild the annual internal audit plan here; that is CIA Part 3 / GIAS Domain IV. Stay inside one engagement.

Mandatory versus recommended in the 2024 IPPF

The International Professional Practices Framework has three layers. Mixing them up is a high-yield exam error.

  • IPPF component Status What it does in engagement planning
  • Global Internal Audit Standards Mandatory How you plan, gather evidence, conclude, and communicate

Topical Requirements Mandatory for assurance when the topic is in scope; recommended for advisory services A minimum baseline of relevant criteria for governance, risk management, and control processes on that topic

Global Guidance (GTAGs, Global Practice Guides, Topical Requirement user guides) Recommended How-to help, examples, and mappings to frameworks such as NIST CSF 2.0 or COBIT 2019

Topical Requirements “provide a minimum baseline and relevant criteria for a consistent, comprehensive approach” to assessing design and implementation of governance, risk management, and control processes in particular risk areas. They are not intended to cover every aspect you might consider. The organization's risk profile may require more. They are also not a requirement to adopt NIST, COBIT, or ISO; if management already uses those frameworks, you reconcile your intended testing to the Topical Requirement so the baseline is covered.

Each Topical Requirement becomes effective 12 months after issuance . Early adoption is encouraged. Quality assessments conducted after the effective date evaluate conformance, including whether engagement files show the applicability assessment.

As of 2026, issued topics include Cybersecurity (effective 5 February 2026), Third-Party (effective 15 September 2026), Organizational Behavior (effective 15 December 2026), and Organizational Resilience (effective 30 April 2027). The IIA's CIA policy is that scored exam questions on a new Topical Requirement do not appear until at least six months after that requirement's effective date . For Cybersecurity, that window opened about 5 August 2026. The 2025 Part 2 syllabus has tested how to apply Topical Requirements in planning since 28 May 2025, so treat the method as always in play and treat Cybersecurity as the working example the IIA actually published first.

When the requirement applies — three triggers

The Cybersecurity Topical Requirement (and the same pattern on later topics) is applicable when the topic is one of the following:

  • A. The subject of an engagement in the internal audit plan
  • B. Identified while performing an engagement
  • C. The subject of an engagement request not on the original internal audit plan

Evidence that each requirement in the Topical Requirement was assessed for applicability must be documented and retained. Not every individual requirement applies in every engagement. If you exclude requirements, a rationale must be documented and retained . Rotational coverage across more than one engagement can be a valid rationale; “we ran out of hours” without a risk basis is not.

Conformance is mandatory for assurance and recommended for advisory. Relabeling an assurance engagement as “advisory” after you find a cyber issue, solely to dodge the baseline, is not a planning technique — it is a quality-assessment finding waiting to happen.

Cybersecurity as the planning example — not a CISSP chapter

The Cybersecurity Topical Requirement uses NIST's short definition of cybersecurity (protect or defend the use of cyberspace from cyberattacks) and treats cybersecurity as a subset of information security (confidentiality, integrity, and availability). For Part 2 planning you need the three-pillar baseline , not a catalog of controls.

Governance (planning questions). Is there a formal cybersecurity strategy and objectives, updated and reviewed by the board, including resources and budget? Are policies and procedures established and updated? Are roles and responsibilities defined, with a process to assess knowledge, skills, and abilities? Are relevant stakeholders — senior management, operations, risk, HR, legal, compliance, vendors — engaged on vulnerabilities and emerging threats?

Risk management (planning questions). Do enterprise risk processes identify, analyze, mitigate, and monitor cyber threats against strategic objectives ? Is cyber risk management cross-functional, not only an IT silo? Is an individual or team accountable for monitoring and reporting, including resources and emerging threats? Is there a process to escalate risk that reaches an unacceptable level, considering financial and nonfinancial impact? Is awareness training in place, with management review of gaps and remediation? Is incident response and recovery defined (detection, containment, recovery, post-incident analysis) and periodically tested ?

Control processes (planning questions). Are internal and vendor-based controls in place to protect confidentiality, integrity, and availability, and periodically evaluated? Is there a talent process for technical competency? Is there continuous monitoring of threats and improvement opportunities? Is cybersecurity built into the IT-asset life cycle (selection, use, maintenance, decommissioning)? Are strengthening processes such as configuration, encryption, patching, and user-access management in place? Network and endpoint controls exist in the requirement (segmentation, firewalls, VPN/ZTNA, IDS/IPS, email and file-sharing). For this exam, that list tells you what you may need a specialist to test , not how to configure a firewall. Chapter 4 covers cybersecurity, IT general controls, privacy, and data security as planning knowledge in more operational depth.

The companion user guide maps the baseline to NIST CSF 2.0, NIST SP 800-53, and COBIT 2019. Mapping is recommended help. It does not replace documenting applicability.

Four planning implications you must be able to apply

1. Required risk and control considerations. Once the topic is in scope, the three pillars become default risk/control questions for the work program. You do not invent a parallel private framework. You also do not copy every control-process letter into an accounts-payable test of a web purchase-order portal. Professional judgment (GIAS 13.2, 13.3, 13.4, 13.6) decides which requirements are applicable to this engagement's objectives.

2. Evidence you will need. Planning fails if you discover in week three that board cyber reporting, the last tabletop of the incident-response plan, or vendor SOC reports are not obtainable in the fieldwork window. Typical evidence to schedule up front includes: the cyber strategy and last board or committee pack; policy set and last-review date; CISO (or equivalent) charter, reporting line, and competency assessments; risk-register entries and appetite/tolerance statements; incident-response plan and last test results; vendor SOC reports and contract security clauses; and extracts that will support later testing of access, patching, or encryption if those control-process requirements stay in scope.

3. Specialists you may need. If the internal audit function lacks the knowledge to perform the in-scope work, obtain it — co-source or outsource — under competency and human-resources standards. Outsourcing does not transfer conformance responsibility; the chief audit executive remains responsible for the Topical Requirement. If resources are still insufficient, that limitation must be recognized in planning (and, under GIAS, raised as a resource issue). For a portal-only slice of AP, you may need a short specialist review of authentication and data-in-transit protections rather than a full red-team.

4. Interaction with engagement objectives already set. Objectives and scope decide whether the topic is in. Planning decides which requirements you will cover, what evidence you will collect, and who will do the work. You do not rewrite a three-way-match objective into “audit the enterprise cyber program” merely because a Topical Requirement exists. You also do not ignore a web portal that sits inside an AP walk-through. The IIA's own user-guide example is exactly that: AP was not scoped as a cyber engagement; the walk-through showed web-based purchase-order submission; Standard 13.2 then required a fresh look at the Cybersecurity Topical Requirement; governance or full risk-management pillars might be excluded with a documented rationale if they are not relevant to the portal risk.

In practice

You are planning AP. Objectives are accuracy, timeliness, and vendor-master integrity. Scope originally excluded “IT security.” The walk-through shows vendors upload invoices to an internet-facing portal. Planning response: assess the Cybersecurity Topical Requirement for applicability; keep AP objectives; add the portal-related control-process and risk-management requirements that protect invoice integrity and vendor identity; exclude enterprise cyber-strategy testing with a written rationale; request a specialist for portal authentication if the team cannot evaluate it; schedule evidence (SOC report for the portal vendor, access listings, incident logs for the portal). That is A3a. It is not an invitation to write a CISSP study guide inside an AP file.

Loading diagram... Topical Requirements in Engagement Planning