PracticeISCFree practice exam

ISC · Security and Confidentiality and Privacy · 6 practice questions

Penetration Test Authorization and Cloud Scope Rules

Intrusive penetration testing requires written authorization and defined scope, timing, and rules of engagement, including cloud-provider restrictions. Below, follow a customer portal test from initial approval through permitted testing alternatives.

The ruleBefore intrusive testing, obtain written authorization and define targets, permitted techniques, timing, contacts, and stop conditions. Follow cloud-provider restrictions; verbal instructions do not expand the signed scope.

Try one first

A company engages an external security firm to perform a penetration test of its internet-facing production systems. Management wants the test to be realistic but also controlled and authorized. Which response is most appropriate before testing begins?
Hint

Focus on what must be in place to make a penetration test both realistic and properly controlled.

Step by step

  1. Obtain written authorization

    A company plans a penetration test of its customer portal in a shared cloud environment. Obtain written authorization before intrusive testing begins.

  2. Identify permitted targets

    List the approved portal assets and check the cloud provider's restrictions. Company approval does not authorize testing provider-managed infrastructure that the provider excludes.

  3. Define allowed techniques

    Specify permitted scanning and exploitation; exclude phishing and denial-of-service testing unless authorized. Verbal instructions cannot expand the signed scope, even after a serious finding.

  4. Choose a safe testing window

    Document when testing may occur and assess the portal's expected transaction volume. Peak transaction activity supports narrowing or rescheduling the test, even when authorization is already signed.

  5. Set contacts and stop conditions

    Document emergency contacts, escalation procedures, and conditions that require testing to stop. Production testing is not automatically prohibited, but it must remain within approved limits.

  6. Authorize a permitted alternative

    If the planned production test is prohibited, do not perform it. Determine whether application-layer testing or testing in a production-mirrored staging environment is permitted, and obtain written authorization covering the alternative targets and techniques.

Key points

  • Remember: Realism does not grant permission; the approved scope determines which targets and techniques testers may use.
  • A serious finding justifies requesting a scope change, not performing an excluded procedure.
  • Company approval cannot override a cloud provider's restrictions.

How the exam traps you

  • Treating verbal permission as approval to expand testing. Obtain a formally approved written scope change before using additional targets or techniques.
  • Assuming company authorization permits testing shared cloud infrastructure. Check provider restrictions and limit testing to permitted assets and methods.
  • Proceeding during peak transaction volume because authorization is signed. Reassess disruption risk and narrow or reschedule the test.

5 more, each from a different angle

0 of 5 answered · 0 correct

Question 2

An auditor planned penetration testing of a client's cloud-hosted financial application as part of controls testing. The hosting provider prohibits intrusive testing on production systems and the client will not request an exception. The client provided a SOC 2 Type II report covering Jan-Dec Year 1. In early Year 2 (after the SOC 2 period) the client implemented a single sign-on (SSO) integration that affects access to the application, a key control over financial transactions. Given the prohibition on intrusive production testing, what is the auditor's best action?
Hint

Compare the SOC 2 report period to the SSO change and think about what alternative evidence (vendor test reports, change‑management/configuration records, provisioning tests, log review, or nonproduction testing) can address the gap when production penetration testing is prohibited.

Question 3

A company plans an external penetration test of its production online payment portal. The engagement has written authorization, a defined scope, and emergency contacts in place. Which additional fact would most strongly support limiting the test or rescheduling it rather than proceeding as planned?
Hint

Look for the fact that changes whether a valid security test should occur in production at that specific time.

Question 4

Company Orion operates an internet-facing web application hosted by a cloud service provider (CSP). In Year 1 the development team deployed a significant update that added a new authentication module and several API endpoints. Company policy requires comprehensive security testing within 30 days after major changes. The CSP's contract expressly prohibits unauthorized active penetration testing of its managed infrastructure and requires penetration tests be scheduled or performed by CSP-approved testers; obtaining authorization typically takes 2-3 weeks. Orion maintains a staging environment that mirrors production and has source code access for the new module. Which of the following is the most appropriate next step?
Hint

Weigh the CSP's restriction on intrusive tests against the 30-day testing requirement, what lawful, lower-impact activities can you do now while arranging any authorized tests?

Question 5

Company X operates an online consumer portal that processes full Social Security numbers (SSNs). The company plans to hire an external vendor to perform a penetration test against the externally facing portal. The vendor will be given credentials for a company-created test user account but has requested permission to attempt exploitation that could, if successful, access production data. From a security, confidentiality, and privacy perspective, which of the following is the most appropriate treatment of this penetration test?
Hint

Think about two things: (1) classification of an active penetration test’s risks for PII and operations, and (2) the controls needed to balance realism with legal/privacy and monitoring requirements.

Question 6

An entity hires an external firm to perform a security test of its public-facing systems. The signed rules of engagement allow vulnerability scanning and limited exploitation of specifically listed hosts, but they expressly exclude phishing and denial-of-service testing. During the kickoff meeting, an operations manager tells the testers to "use any method you think is necessary" if they find a serious weakness. No written change to scope is approved. What should govern which testing procedures the firm may perform?
Hint

Focus on what formally authorizes testing activity, not on what seems useful in the moment.

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 must be documented before a penetration test?

Obtain written authorization and document target assets, allowed techniques, testing windows, emergency contacts, and stop conditions. Include any cloud-provider restrictions.

Can verbal approval override penetration testing rules of engagement?

No. Signed scope and rules of engagement govern the test; additional procedures require a formally approved written change.

What if a cloud provider prohibits production penetration testing?

Do not perform the prohibited test. Consider application-layer or staging tests only if those targets and techniques are permitted and covered by written authorization.

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.