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.
Try one first
Hint
Focus on what must be in place to make a penetration test both realistic and properly controlled.
Answer C. Penetration testing should be formally authorized and bounded before it starts. Written authorization and clear rules of engagement define the scope, timing, allowed techniques, and responsibilities, which reduces legal and operational risk and prevents unintended disruptions. This is the best response when testing production systems.
Why not A: A completely undisclosed test might better simulate an attacker, but appropriate internal authorization and coordination are needed to manage safety and avoid confusion or false incident responses. At minimum, system owners and key operations staff should be aware enough to mitigate risks.
Why not B: This seems realistic, but even realistic testing must stay within an approved scope. Allowing testers to target any discovered systems creates legal, operational, and governance risks and can lead to unapproved disruption.
Why not D: Testers' primary role is to identify and document weaknesses; requiring immediate remediation undermines the engagement and may conflict with normal change-management processes. Remediation should be planned and executed by the organization's owners after validation.
Step by step
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
Question 2
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.
Answer A. Intrusive production testing is prohibited and the SOC 2 report covers a prior period, so the auditor should not perform the blocked test or rely solely on the historical SOC 2. The auditor should evaluate the SOC 2 and any more recent vendor test reports and obtain targeted, nonintrusive evidence for the post‑SOC 2 SSO change (change‑management, configuration and provisioning tests, and log review). Any remaining need for direct testing should be limited to nonproduction or performed only with explicit vendor permission, and the auditor should document any limitation.
Why not B: Tempting because a SOC 2 Type II is third‑party assurance, but wrong because the report is historical (Year 1) and may not cover the Year 2 SSO integration or current application settings; relying on it alone can leave the auditor without sufficient, appropriate evidence for the changed control.
Why not C: Tempting because direct testing provides strong evidence and obtaining permission seems logical, but wrong because deferring targeted alternative procedures while waiting for permission is inadequate; the auditor cannot compel the provider and should pursue other evidence (vendor reports, nonintrusive procedures, or nonproduction testing) rather than relying only on inquiry.
Why not D: Tempting as a conservative response, but wrong because an immediate qualification or withdrawal is premature; auditors must first attempt reasonable alternative procedures and evaluate other evidence sources before concluding a scope limitation that would require modifying the opinion.
Question 3
Hint
Look for the fact that changes whether a valid security test should occur in production at that specific time.
Answer D. Even an authorized penetration test can impact system performance or availability. Performing the test during the portal's annual peak transaction period greatly increases the risk of significant business disruption, so management should narrow the scope, reschedule, or use safer testing approaches.
Why not A: This is tempting because 'manual exploitation' sounds aggressive, but combining automated and manual methods is normal for a penetration test. With proper authorization and controls, that fact alone doesn't justify delaying or limiting a test.
Why not B: Credentialed test accounts can sound risky, but when accounts are dedicated, controlled, and monitored for the engagement they often reduce collateral risk and improve test accuracy; this practice by itself doesn't require postponement.
Why not C: Candidates may think a recent scan with only medium findings makes further testing unnecessary. However, penetration testing seeks different types of vulnerabilities and test timing risk is about business impact, not the scan's recent results.
Question 4
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?
Answer B. The CSP contract forbids unauthorized active testing, so any intrusive penetration test must be coordinated and scheduled with the CSP. Because authorization can take 2-3 weeks and company policy requires testing within 30 days, performing credentialed DAST plus a focused SAST/code review in staging provides immediate, lower-risk coverage and allows prompt remediation while the authorized penetration test is arranged.
Why not A: Tempting because it's quick and minimally disruptive and gives early findings. However, running an uncoordinated scan may violate the CSP contract and risk service disruption, and unauthenticated scans miss authentication- and business-logic vulnerabilities that credentialed DAST and code review would better detect.
Why not C: Tempting because active exploitation can demonstrate real-world impact and prioritize fixes. But doing intrusive penetration testing in production without CSP authorization would breach the contract, create legal and outage risks, and is not permissible; such testing must be scheduled per the CSP's requirements.
Why not D: Tempting because it follows the established schedule and avoids ad hoc activity. However, deferring ignores the policy requiring testing within 30 days after major changes and leaves new authentication risks unaddressed when lawful, lower-risk activities (credentialed DAST and code review in staging) are available now.
Question 5
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.
Answer A. Penetration testing that may touch PII requires formal authorization and a narrowly defined scope to manage legal and operational risk. Use of test accounts and masked or sanitized data protects confidentiality; keeping monitoring/logging enabled preserves evidence and allows detection of unintended effects. Advance notification to operations and legal, plus backup and rollback plans, mitigate service-disruption and privacy risks while still allowing realistic testing.
Why not B: This option is tempting because testing with real data and reducing noisy alerts may seem to produce clearer results, but it is wrong: disabling detection removes visibility and increases operational and security risk, and using live customer accounts/data exposes PII without proper controls or consent. Additionally, a vendor report alone does not replace preserved monitoring evidence and formal authorization.
Why not C: This distractor appeals to a conservative privacy interpretation and the lower risk of scans, but it is incorrect: privacy obligations do not categorically prohibit controlled penetration testing conducted under proper safeguards. Automated scans also often miss complex attack paths that active testing can reveal, so scans alone may be insufficient for a high-risk system.
Why not D: This choice is attractive because scheduling and reducing impact seem cautious, but it is wrong: taking the portal offline prevents testing of live defenses and produces less realistic results, using production data still creates privacy exposure, and relying on a generic engagement letter fails to define approved methods, scope, and explicit kill criteria necessary for legal and operational safety.
Question 6
Hint
Focus on what formally authorizes testing activity, not on what seems useful in the moment.
Answer C. Formally approved scope and rules of engagement control what testing procedures are authorized. They define permitted methods, target assets, and explicit exclusions; informal or verbal instructions do not override written authorization. If additional procedures are needed, testers should seek a formal scope change or written approval before proceeding.
Why not A: A verbal comment may seem like permission, but verbal changes do not supersede written engagement terms; scope must be changed through formal, documented approval.
Why not B: Experienced testers use professional judgment, but that judgment must operate within the authorized scope; it does not authorize procedures that the engagement expressly excludes without formal approval.
Why not D: High-severity findings may justify requesting broader testing or escalation, but they do not automatically authorize testers to perform methods that were explicitly excluded by the approved scope.
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
- Vulnerability Scan vs. Penetration Test: Which to Use?
- When to Use Vulnerability Scanning vs Penetration Testing
- PII in Test Environments: Masked vs. Unmasked Data
- Testing Automated Access Controls Across the Audit Period
- 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.