CPSA ยท Engagements, law and reporting
Testing risks and DoS planning
Risks a test introduces, risk levels, mitigation, test windows, backups and planning for denial-of-service side effects.
Key points
- Testing can itself cause harm: crashed services, locked accounts, filled disks, corrupted data.
- Manage this by rating risk (likelihood and impact), agreeing test windows, confirming backups and restore ability, throttling aggressive scans, avoiding destructive checks on production unless approved, and keeping an emergency contact.
- Denial-of-service side effects are planned for, not discovered by accident.
Practice questions
Which measure best limits the impact if a test crashes a production system?
- Verified backups and a tested restore process
- A longer report
- Using more scanners at once
- Testing during peak trading hours
Show answer
Answer: A. Verified backups and a tested restore process
Backups you can restore turn an outage into a recoverable event. The other choices do nothing for recovery or raise the risk.
Which side effects of testing should be planned for?
- Account lockouts from password guessing
- Services slowing or stopping under heavy scans
- Free upgrades to the client's hardware
- Automatic regulator approval
- Guaranteed zero downtime
Show answer
Answer: A. Account lockouts from password guessing, B. Services slowing or stopping under heavy scans
Lockouts and load effects are real and common. Nothing guarantees zero downtime, so risk is managed, not removed.
Using the fastest scan timing is always safe if the target is in scope.
Show answer
Answer: False
Being in scope permits testing, not damage. Fast settings raise the chance of overloading fragile services, so rates are tuned.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
