PracticeISCFree practice exam

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.

The ruleBase testing type, scope, and frequency on a documented risk assessment of data sensitivity, exposure, threat likelihood, impact, and significant changes. Meet required testing minimums, but test sooner or more deeply when current risk warrants it.

Try one first

An organization runs an internet-facing application that stores highly sensitive personal data and is updated several times per month. Its external regulator requires an annual penetration test for critical systems. Management proposes limiting tests to that annual schedule to save budget; developers want tests after each release. Assuming no other legal or contractual mandates require more frequent testing, which single factor should govern the application's testing frequency and scope?
Hint

Think about whether compliance minimums, release cadence, or resource limits should override a single, organization-level determination of testing needs.

Step by step

  1. 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.

  2. 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.

  3. Map the affected controls

    Identify how the migration changed cloud configuration, API access, and authentication. Include connected access paths that could expose customer PII.

  4. 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.

  5. 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.

  6. 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.

6 more, each from a different angle

0 of 6 answered · 0 correct

Question 2

A company that stores customer personal information made significant changes in 20X6 to its identity-and-access management system and its encryption module. Both controls were tested successfully in 20X5. Assume the 20X6 changes could affect how the controls operate. What is the correct treatment for testing these controls?
Hint

Focus on what should happen when key security controls are modified, not just on the normal testing calendar.

Question 3

TechCo operates a production SaaS application. Its security program runs automated vulnerability scans monthly and a third‑party penetration test annually (last performed 10 months ago). Five weeks ago TechCo migrated its core production application to a new cloud provider (a significant architecture and configuration change). Last week log monitoring detected multiple unusual authentication attempts from foreign IP addresses and one successful administrative login; initial review has not confirmed data exfiltration or system compromise. Considering standard security‑testing best practices (timing and triggers), what is the most appropriate timing or trigger for additional security testing? (Testing and incident investigation may proceed in parallel.)
Hint

Ask whether a recent large infrastructure change plus anomalous administrative activity should trigger out‑of‑cycle, targeted testing beyond routine scans.

Question 4

Delta Co. stores employee Social Security numbers and direct-deposit information in a cloud HR platform that is accessible over the internet. During Year 2, Delta added employee mobile access and changed the identity-management service used for login. Management is deciding how extensive and how frequent security testing should be for this platform. Assume no law, regulation, or contract sets a fixed testing schedule. Which factor should primarily govern Delta's testing approach?
Hint

Ask what should drive the nature, timing, and extent of security testing when no outside rule sets a fixed schedule.

Question 5

A company that stores confidential business data and customer PII wants to conclude that its ransomware recovery capabilities were adequately tested in Year 2. During Year 2, it performed: (1) a cross-functional tabletop exercise for ransomware response, (2) a failover test to the disaster recovery environment using masked production data, and (3) inspection of backup logs showing nightly encrypted backups completed successfully. Midyear, the company replaced its backup software and changed the integration used to access decryption keys for backups. It did not perform any restore test from backup sets created after that change. Assume the question is only about the sufficiency of testing evidence, not legal notification requirements. Which fact is the strongest limiting condition on management's conclusion?
Hint

Separate evidence that backups ran from evidence that backups can actually be restored after a significant change.

Question 6

An entity that stores customers' tax records completed an enterprise-wide external penetration test in Month 2 of Year 2 with no high-risk findings. In Month 8, it moved remote-access authentication to a cloud identity provider, opened a new API connection to a payroll processor, and revised firewall rules to permit the API traffic. Since those changes, authenticated vulnerability scans of servers and network devices have shown no critical vulnerabilities, and a walkthrough confirmed the API functions as intended. Management now wants the most effective test to determine whether the recent changes created a practical path to unauthorized access or exfiltration of confidential data before peak season. Assume there is no known breach and no legal or contractual requirement for a full enterprise-wide retest at this time. What is the best action?
Hint

Ask which test best evaluates the combined exploitability of several recent system changes, not just whether individual settings or user entitlements look acceptable.

Question 7

Riverton Financial Services operates an internet-facing web application that stores customer PII and processes payment card transactions. Its security program includes authenticated automated vulnerability scans of internet-facing systems every month (critical findings are remediated within 30 days) and external full-scope penetration tests performed every 24 months. A prior monthly scan detected a critical vulnerability that was remediated within 28 days, but a later attack exploited a chained attack path that was discovered only by a penetration test. Based on these facts, which conclusion is best supported about Riverton's testing program and its ability to provide assurance over confidentiality and privacy controls?
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.

Drill all 138 Testing questionsMixed across every rule in the topic, so you have to spot which one applies. That is how the exam does it.

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

All Testing practice →

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.