ISC · Security and Confidentiality and Privacy · 7 practice questions
What Drives Security Testing Scope and Frequency?
Current risk should drive security testing scope and frequency, not the annual calendar alone. Follow a portal migration to see why changed controls need targeted testing before the next scheduled test.
Try one first
Hint
Think about whether compliance minimums, release cadence, or resource limits should override a single, organization-level determination of testing needs.
Answer D. Testing frequency and scope should be determined by a documented, organization-wide risk assessment that weighs data sensitivity, system exposure, likelihood and impact of threats, and how often the system changes. Regulatory requirements typically define minimums and do not prevent more frequent testing when risk is higher. Therefore change frequency is an input to the risk assessment, not the sole governing factor; a highly exposed, frequently updated app holding sensitive data will often justify testing more often than the compliance floor.
Why not A: Tempting because regulatory schedules are concrete and auditable. It fails as the governing factor because regulators usually set minimum standards; relying only on the regulator's calendar can leave high-risk systems under-tested when operational risk exceeds the compliance minimum.
Why not B: Tempting because frequent changes increase the chance of introducing vulnerabilities. It fails as the single governing factor because not every change materially alters risk; testing every release can be inefficient or misprioritize effort unless changes are assessed within a risk-based framework.
Why not C: Tempting because resources limit what is feasible in practice. It fails as the governing principle because budget and staffing are implementation constraints, not the determinant of what needs testing; priorities should be set by risk and resources allocated or supplemented accordingly.
Step by step
- Identify the changed environment
Ridge's internet-facing portal stores customer PII and requires annual penetration testing. After a clean annual test, Ridge migrates it to a new cloud environment, adds a public API, and changes login to SSO; subsequent vulnerability scans find no critical issues.
- Assess current risk
Document data sensitivity, external exposure, threat likelihood, and potential impact. Evaluate the portal as it operates after migration, not as it existed during the annual test.
- Map the affected controls
Identify how the migration changed cloud configuration, API access, and authentication. Include connected access paths that could expose customer PII.
- Choose tests that address exploitability
Perform a focused penetration test of the migrated portal, public API, and SSO flow, supported by a cloud-configuration review. Clean vulnerability scans do not establish whether these components create a chained attack path.
- Test before the annual cycle
The material changes warrant targeted testing now rather than waiting for the next annual test. The clean prior result does not validate the new implementation.
- Keep the scope proportional
Retain the broader annual testing schedule for unchanged systems unless the assessment identifies wider effects. Document why the selected scope, depth, and timing address the migration's risks.
Key points
- Remember: A clean test covers the old configuration, not significant changes made afterward.
- Nature means test type; timing means when; extent means coverage and depth.
- An annual testing requirement sets a floor, not a ceiling.
How the exam traps you
- Wait for the annual test because the last test was clean. Assess the new exposure and test materially changed controls now.
- Treat scans with no critical findings as proof that the migration is secure. Use targeted penetration testing to evaluate exploitable paths that scans may miss.
- Repeat the entire enterprise penetration test after any significant change. Scope the retest to changed components and affected paths unless risk extends further.
Question 2
Hint
Focus on what should happen when key security controls are modified, not just on the normal testing calendar.
Answer B. Significant changes to security-related systems can alter how controls operate; prior successful testing in 20X5 does not guarantee continued effectiveness after 20X6 changes. Therefore, additional testing after the changes is required to confirm the controls still achieve the security and confidentiality objectives.
Why not A: Tempting because the objectives remained the same, but testing evidence is less persuasive when the underlying systems have changed. Prior results alone are insufficient when changes could affect control operation.
Why not C: Appealing due to routine annual schedules, but significant changes are a trigger for additional testing; waiting for the calendar or a breach would risk undetected control failures.
Why not D: This narrows testing to the obvious technical change, but the stem states both the identity-and-access system and the encryption module changed. Both changed controls should be retested if the changes could affect operation.
Question 3
Hint
Ask whether a recent large infrastructure change plus anomalous administrative activity should trigger out‑of‑cycle, targeted testing beyond routine scans.
Answer D. A recent, significant architecture/configuration change (the cloud migration) combined with suspicious administrative authentication attempts are recognized triggers for out‑of‑schedule testing. Best practice is to perform an immediate, targeted vulnerability assessment and a focused penetration test of the changed environment and implicated access paths, remediate findings promptly, and conduct follow‑up testing to verify fixes. Routine monthly scans and the next scheduled annual penetration test alone are insufficient to validate exploitability or confirm that access controls are effective after such changes.
Why not A: This is tempting because TechCo already runs monthly scans and has an upcoming annual pentest, which conserves resources. It fails because a major migration plus anomalous admin activity are explicit triggers for targeted, out‑of‑cycle testing, routine schedules may not detect new misconfigurations or validate exploitability promptly.
Why not B: This seems prudent since forensics determine scope and evidence. It is wrong because waiting for confirmed compromise can allow exploitable vulnerabilities or active attackers to persist; proactive targeted testing is warranted when high‑risk indicators are present even without confirmed exfiltration.
Why not C: This choice is appealing because scans are quick and part of the normal program. It is incorrect because automated scans may miss chained exploits or the real‑world exploitability of access paths; given the migration and suspicious login activity, a focused penetration test should be performed promptly in addition to scans, not deferred.
Question 4
Hint
Ask what should drive the nature, timing, and extent of security testing when no outside rule sets a fixed schedule.
Answer C. Security testing should be driven primarily by risk. Because the system holds highly sensitive data, is internet-accessible, and recently underwent changes to access and authentication, those factors increase the need for targeted and possibly more frequent testing. In the absence of a fixed external schedule, a risk-based plan best determines the nature, timing, and extent of testing.
Why not A: This is tempting because auditors coordinate control testing with financial statement work, but audit timing is not the primary driver of security-testing decisions. The audit schedule may affect coordination, but testing scope and frequency should reflect the system's security risk.
Why not B: Past clean results can be reassuring, but they do not override current conditions. Significant new exposures or changes (sensitive data, internet access, and identity-management changes) require testing decisions based on present risk, not only last year's findings.
Why not D: Budget constraints are a practical consideration, but they should not be the primary basis for determining testing extent or frequency. Management should prioritize risk and then allocate resources accordingly, rather than letting remaining funds dictate testing plans.
Question 5
Hint
Separate evidence that backups ran from evidence that backups can actually be restored after a significant change.
Answer D. This is the strongest limiting condition because successful backup jobs and a failover to a DR environment do not prove that backups created after a significant backup-platform and key-access change are actually restorable. The critical risk is that the new software or changed key integration could prevent decryption or timely restoration; only a restore-from-backup test on post-change sets directly demonstrates recoverability within the recovery objective.
Why not A: Tempting because cross-functional participation matters for coordinated incident response and messaging, but this omission affects the completeness of the exercise rather than the core technical question of whether encrypted backups created after a platform/key change are decryptable and restorable.
Why not B: Tempting because some might assume only live data validates a recovery, but masked production data is commonly used to test failover processes safely and can be sufficient for validating technical failover steps. The more serious limitation here is the absence of a restore test after the backup/decryption integration changed.
Why not C: Tempting because unannounced tests can reduce rehearsal effects and reveal operational weaknesses, but a scheduled failover can still provide meaningful technical evidence if executed properly. This timing issue is less limiting than not verifying that post-change encrypted backups can actually be decrypted and restored.
Question 6
Hint
Ask which test best evaluates the combined exploitability of several recent system changes, not just whether individual settings or user entitlements look acceptable.
Answer D. A targeted penetration test best evaluates whether the combination of recent changes created an exploitable path to unauthorized access or data exfiltration. The prior enterprise-wide test did not assess the new identity provider, API integration, or revised firewall rules together, and vulnerability scans do not simulate chained exploitation across those trust boundaries. A scoped retest focused on the changed components is more efficient and appropriate than an immediate full enterprise retest given the assumptions.
Why not A: Tempting because of the recent clean enterprise test and scan results, but wrong: significant architecture and integration changes can introduce new multi-step attack paths that were not present during the prior test, so deferral leaves a plausible risk untested.
Why not B: Access recertification assesses whether user entitlements remain appropriate, but it does not test whether the new end-to-end design or configuration interactions can be exploited to bypass controls or exfiltrate data across the new trust boundaries.
Why not C: Although scans are efficient for finding known component vulnerabilities, they do not adequately evaluate whether multiple changes can be chained into a real exploit across authentication, firewall rules, and external API integrations; they miss many practical attack paths that a penetration test would simulate.
Question 7
Hint
Differentiate what automated vulnerability scans typically detect versus what penetration tests attempt to demonstrate, and consider the system’s risk profile (internet‑facing + payment processing) when evaluating testing frequency.
Answer D. Automated vulnerability scans are useful for identifying known, individual vulnerabilities but often do not demonstrate exploitability or detect multi-step attack chains. For a high-risk, internet-facing application that processes payment card data, external penetration testing should be more frequent and performed after material changes so chained exploits are discovered in a timely manner. Waiting 24 months between full-scope penetration tests leaves a substantial detection gap and therefore provides insufficient assurance over confidentiality and privacy controls in this high-risk context.
Why not A: Tempting because monthly scans and timely remediation are important continuous controls; wrong because automated scans and distant, infrequent penetration tests are not interchangeable. Scans commonly miss chained or multi-step exploit paths that penetration tests are designed to reveal, so a 24-month interval is likely too long for this high-risk environment.
Why not B: Tempting because timely remediation of critical findings is a strong control; wrong because remediation cadence alone doesn't address detection gaps. Discovering a chained attack path only during a penetration test indicates the monitoring program failed to identify an exploitable multi‑step path in a timely way, so testing frequency and capability are also deficient for this risk profile.
Why not C: Tempting because it emphasizes the value of penetration testing over simple scans; wrong because it proposes abandoning continuous scanning altogether. Scans and penetration tests are complementary, scans provide ongoing coverage while penetration tests validate exploitability and find chained attack paths, so discontinuing scans would remove an important detection capability.
Common questions
What should determine security testing scope and frequency?
A documented assessment of current risk should govern. For Ridge's portal, sensitive customer data, internet exposure, threat likelihood, and the migration determine what to test, how deeply, and when.
Is another security test needed after a cloud migration?
Ridge's migration changes hosting, public API exposure, and authentication, so targeted testing is warranted now. The prior clean annual test did not cover those changes.
Does a significant change require a full penetration retest?
Not automatically. Test the changed portal, API, SSO flow, and affected attack paths; keep the broader annual schedule for unchanged systems unless the risk assessment identifies wider effects.
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
- Testing Automated Access Controls Across the Audit Period
- Penetration Test Limits: Point in Time and Scope
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.