ISC · Security and Confidentiality and Privacy · 7 practice questions
Testing Automated Access Controls Across the Audit Period
Testing automated access controls across a period requires evidence of actual execution, not just current settings. Below, sort Nova's audit procedures for automated payroll access before and after a July HR-interface change.
Try one first
Hint
Think about which procedures produce evidence about both control design and consistent operation across the entire six-month period (not just a single point in time or unrelated technical tests).
Answer A. This set of procedures addresses both design and operating effectiveness: inspecting configuration and approval settings evaluates control design, reviewing system-generated logs across the full six months and re-performing approvals sampled from different months provides direct evidence the approval workflow operated consistently over the period, and checking membership-change logs confirms that only authorized approvers could act.
Why not B: Tempting because inquiry and observation confirm existence and policy, but a single observed event and management inquiry do not demonstrate consistent operation over the entire six-month period and do not test platform configuration or historical system logs.
Why not C: Snapshot re-performance shows the control at one point in time only and can miss intermittent failures earlier in the six-month period; without historical logs or sampling across the period, operating effectiveness is not demonstrated.
Why not D: External assurance and technical tests are useful, but a SOC 1 may not cover the client's specific provisioning workflow or operating results, and vulnerability/penetration testing assesses technical vulnerabilities rather than whether the approval workflow and logs actually operated effectively across the six-month period.
Sort it
Does the procedure examine actual historical access events, including the changed interface when relevant?
Does the procedure show intended operation or current behavior without testing historical execution?
Does the conclusion extend reliance after July without sufficient evidence for the changed workflow?
| Item | Goes to |
|---|---|
| Trace sampled Nova provisioning events from before and after July through approval records, system logs, and resulting payroll roles. | Supports period-wide testingThis tests actual approvals and role assignments across both versions of the interface. |
| Inspect Nova's current role-based access control configuration and conclude it operated effectively all year. | Design or snapshot evidence onlyCurrent settings show intended restrictions, not whether those restrictions operated throughout the year. |
| Rely on successful June testing through December because Nova reported no unauthorized access after migration. | Leaves a post-change evidence gapJune testing does not establish operation of the changed interface. No reported misuse does not supply the missing evidence. |
| Compare sampled HR termination timestamps with account-disablement timestamps across Nova's audit period, including after July. | Supports period-wide testingThe comparison tests whether actual account removals occurred within Nova's required timeframe across the period. |
| Create a test user today and confirm Nova's system blocks assignment of a restricted payroll role. | Design or snapshot evidence onlyThis is useful reperformance, but alone it establishes behavior only at the test date. |
| Inspect Nova's revised HR mapping and reperform sampled post-July role assignments using HR records and provisioning logs. | Supports period-wide testingThis directly tests whether the changed interface translated HR data into the intended access. |
| Read Nova's provisioning policy and ask IT whether the automated workflow ran correctly throughout the year. | Design or snapshot evidence onlyPolicy and inquiry describe expected operation without independently verifying historical access changes. |
| Inspect Nova's RBAC settings and compare sampled historical payroll-change logs with users' authorized role assignments. | Supports period-wide testingConfiguration plus historical activity tests whether restricted actions were performed by accounts holding authorized roles. |
| Review Nova's current user listing and confirm that no terminated employees still have payroll access. | Design or snapshot evidence onlyA clean current listing cannot show whether accounts remained active too long earlier in the year. |
| Use a properly designed sample spanning Nova's pre-July and post-July workflows without selecting an event from every month. | Supports period-wide testingSampling can support a period-wide conclusion when it appropriately addresses both workflows and the relevant population. |
| Observe one Nova employee's provisioning during the audit visit and use that observation as the sole annual test. | Design or snapshot evidence onlyOne observed event does not demonstrate consistent historical execution. |
| Accept owner inquiry and successful October testing despite lost July-through-September records and no sufficient alternative evidence. | Leaves a post-change evidence gapSampling need not cover every month, but successful testing elsewhere and inquiry alone do not resolve this known post-migration evidence gap. |
Key points
- Remember: A control working today does not prove it worked throughout the audit period.
- Trace HR events through role assignments or account removal to test whether individual access changes occurred correctly and on time.
- A system change requires post-change evidence; it does not automatically invalidate earlier testing.
- Properly designed sampling can support period-wide conclusions without testing every month.
How the exam traps you
- Treating policies and configuration screenshots as proof of historical execution. Trace actual access changes to approvals, HR records, and system logs across the period.
- Using one successful test account to support the entire year. Combine reperformance with sampled historical events rather than relying on a current snapshot.
- Extending pre-migration results through year-end because no unauthorized access was reported. Test post-migration events and inspect the changed interface before extending reliance.
Question 2
Hint
First classify each control as automated versus manual; then choose procedures that produce direct evidence the control actually operated across periods (reperformance, logs, sampling/vouching) rather than just showing design or locating vulnerabilities.
Answer B. This choice matches the test method to the control type and seeks direct evidence of operation: inspection plus reperformance for automated configuration controls (TLS, encryption, firewall) and sampling/vouching of documented reviews for the manual access-review control. Reperformance and log/record review provide evidence the controls actually operated across periods, whereas interviews, design inspection, or vendor scans alone do not demonstrate consistent operating effectiveness.
Why not A: This is tempting because policies, interviews, and external security reports address intended operation and identify vulnerabilities, but interviews and policy inspection are weak for proving operating effectiveness. External scans and pen tests are point-in-time and do not substitute for reperformance, logs, or sampling that show controls actually operated over time, nor do they adequately test the manual access-review process.
Why not C: Walkthroughs and design inspection are useful to test implementation and design, which is why this option is attractive, but they do not provide sufficient evidence about whether the controls operated effectively over the period under audit. Operating-effectiveness testing requires reperformance, sampling, or log-based evidence beyond a single walkthrough.
Why not D: Relying on vulnerability scans and pen-test reports is tempting because they probe security weaknesses, but such reports are point-in-time and focus on exploitable vulnerabilities rather than demonstrating that routine controls (like quarterly access reviews or scheduled key rotation) were operating effectively. They also may not test the specific configurations and remediation evidence the auditor needs to conclude operating effectiveness.
Question 3
Hint
Focus on the difference between evidence that a control exists and evidence that it actually worked over the entire period.
Answer D. Selecting a sample and comparing termination dates to account disablement timestamps directly tests operating effectiveness by checking whether the control actually worked across multiple instances during the period. It relies on objective system and HR records rather than just policy, management inquiry, or a single observation. Therefore it provides the strongest evidence that the 24-hour requirement was met throughout Year 1.
Why not A: Documented policy shows the control is designed appropriately, but it does not prove the control operated as required during the year; the question asks about operating effectiveness, not just design.
Why not B: Inquiry can help understand the process but is weaker evidence and does not verify actual performance for specific terminations; it cannot by itself demonstrate consistent operation throughout the period.
Why not C: Observation of a single instance confirms that personnel can perform the action at a point in time but does not demonstrate consistent operation throughout the year; a sample of actual terminations is stronger for operating effectiveness testing.
Question 4
Hint
First decide if this is a design or operating‑effectiveness issue, then choose the option that uses evidence (logs mapped to account types, configuration/logging review, reperformance) that shows whether MFA was enforced in practice.
Answer C. The log entries suggest the control may have failed in practice, so this is an operating‑effectiveness issue. Verbal explanations or design/configuration alone are insufficient when evidence indicates possible exceptions. The auditor should expand log review, map sessions to account types, inspect configuration and logging, and reperformance test to determine whether MFA was actually enforced; if confirmed lacking for human sign‑ins, conclude the control is not operating effectively.
Why not A: Tempting because technical tests can reveal vulnerabilities, but incorrect: vulnerability/penetration testing and configuration review do not demonstrate that MFA was applied to the 28 recorded sign‑ins or across account types and time. They fail to address the logging gap and do not replace mapping sessions or reperformance to test operating effectiveness.
Why not B: Tempting because the policy shows a designed control and the owner provided an explanation, but incorrect: when logs indicate possible failures the auditor must obtain substantive evidence of operating effectiveness rather than rely solely on design or oral statements.
Why not D: Tempting because the logs suggest a potential deficiency, but incorrect: formal reporting based on limited evidence risks overstating the issue. The auditor should first expand testing to determine scope, corroborate whether the sessions were human accounts, and identify root cause before issuing a formal deficiency.
Question 5
Hint
Which procedures provide direct, nonintrusive evidence about the operating effectiveness of user provisioning and RBAC (administrative) controls given the limited testing window?
Answer D. Reperforming a sample of provisioning and change transactions and reviewing RBAC assignments provides direct, nonintrusive evidence that Alpha Co.'s administrative controls are operating as designed. Inspecting encryption-related configuration artifacts and vendor access approval records checks whether configurations and maintenance access (which affect confidentiality) are appropriately controlled. This approach yields operating-effectiveness evidence without the production risk of intrusive techniques and avoids relying solely on a vendor SOC report for controls Alpha Co. retains.
Why not A: Tempting because a SOC 2 Type II report gives assurance about the vendor's controls, but wrong because Alpha Co. retains responsibility for provisioning and RBAC configuration; the SOC report does not provide direct evidence that Alpha Co.'s administrative controls are operating effectively.
Why not B: Tempting because penetration testing can reveal technical vulnerabilities, but wrong here because a pen test is intrusive, risks disrupting operations given the single maintenance window, and does not directly reperform or validate the administrative provisioning controls Alpha Co. controls.
Why not C: Tempting because logs can show past access and anomalies, but wrong because log review is indirect evidence that may be incomplete and does not demonstrate that provisioning and RBAC controls are operating as intended or that configurations are correct.
Question 6
Hint
Identify which controls are the customer’s (tenant) responsibility versus the provider’s, and prefer procedures that provide tenant-level, ongoing evidence (configs, logs, and controlled re-performance) instead of only design documents or point-in-time tests.
Answer B. The correct approach obtains tenant-level and process-level evidence of operating effectiveness: inspecting tenant settings and key-management documents verifies that database encryption at rest is actually enabled for Novatech; tracing change tickets to firewall logs confirms approvals were implemented; and inspecting alert logs and incident tickets plus controlled re-performance demonstrates that the SIEM generates alerts, creates incident tickets, and SOC analysts respond within required timeframes. The provider's SOC 2 report supplements but does not replace tenant-level evidence.
Why not A: Tempting because SOC 2 reports, inquiry, and observation are common and efficient audit procedures. It is wrong because the provider's SOC 2 does not attest to tenant-level settings, inquiry and brief observation are limited in time and do not demonstrate consistent operation, and observation alone does not verify automatic ticket creation or retention of incident records.
Why not C: Tempting because vulnerability scans and penetration tests find exploitable weaknesses and can test some detection points. It fails because these are point-in-time security tests that do not directly demonstrate administrative workflows (approved change-ticket implementation) or continuous automated processes (SIEM alerting, ticket creation, and consistent SOC response) over the audit period.
Why not D: Tempting because management representations, policy review, and vendor testing are easy to obtain and document control design. It is incorrect because written representations and policies attest to intent and design, not operating effectiveness; vendor penetration tests and management summaries do not substitute for tenant-level evidence (configurations and logs) or for direct testing of continuous processes.
Question 7
Hint
Focus on the difference between evidence about a control's design or current setup and evidence that it actually operated throughout the period, especially across a midyear change.
Answer C. This approach directly tests operating effectiveness over the entire period rather than only current design. It verifies both that the system generated alerts when it should have and that personnel performed timely reviews and documented dispositions. Including samples from before and after the rule change addresses the period-specific risk introduced by the midyear API deployment.
Why not A: Penetration testing assesses exploitability at a point in time and may reveal weaknesses, but it does not demonstrate that the detective alert-and-review control operated effectively across the period. It also does not provide direct evidence that alerts were generated and reviewed throughout 20X6.
Why not B: Inspecting current configuration and relying on inquiry speaks to design and current state but does not prove historical operating effectiveness, especially across a midyear rule change. Inquiry alone is weaker than inspecting actual alerts and reperformance of selected transactions.
Why not D: Policy-to-configuration comparison helps assess design alignment but does not test whether the control actually operated during the period or whether alerts were triggered and reviewed as required. It fails to produce period-specific evidence of operating effectiveness.
Common questions
How do you test automated user provisioning across an audit period?
Inspect the configuration, then trace sampled HR events through approvals, system logs, and resulting access. Select events across the period, including before and after relevant system changes.
Is inspecting RBAC configuration enough to test operating effectiveness?
No. Configuration inspection shows how role-based access control is set up. Historical logs and event-level tracing show whether authorized roles actually received and exercised the intended access.
Does an HR-system migration invalidate earlier access-control testing?
No. Earlier testing can support the earlier period, but post-migration reliance needs additional evidence. Properly designed sampling is acceptable; inquiry and successful testing elsewhere cannot resolve a known post-migration evidence gap without sufficient alternative evidence.
Watch it solved
A full CPA ISC task-based simulation on Testing, worked step by step.
ITGC Testing: Procedures, Samples & Exceptions | CPA ISC TBS on YouTube
Practice ISC like the real exam
The free ChatCPA simulator: real exam layout, timed testlets, starting with a question on this topic. No account needed to start.
Open the free simulator →More on Testing
- Vulnerability Scan vs. Penetration Test: Which to Use?
- When to Use Vulnerability Scanning vs Penetration Testing
- Penetration Test Authorization and Cloud Scope Rules
- PII in Test Environments: Masked vs. Unmasked Data
- Penetration Test Limits: Point in Time and Scope
- What Drives Security Testing Scope and Frequency?
Questions from the ChatCPA bank of 17,658 CPA exam questions, each with a written reason for every wrong answer. ChatCPA is built by Nicholas Miller, CPA (Oregon #14907). How these pages are made. Spot an error? Tell us.