During an infrastructure security review of a high-frequency financial transaction processing service, security operations observed that active credentialed vulnerability scanning triggered service account lockouts and unacceptable latency spikes on production database nodes. The engineering team requires an assessment approach that identifies software security flaws and system configuration weaknesses without initiating active network probes, modifying authentication states, or disrupting live operations. Which security testing methodology best addresses these operational constraints?
- Deploy passive network traffic monitoring alongside offline static application security testing (SAST) of codebase repositories.Cevap
- BDeploy high-interaction honeypots inline within the production network path to intercept scan traffic and dynamically absorb service account authentication attempts.
- CReconfigure perimeter firewall rules to block SQL injection payloads from entering internal database segment interfaces during vulnerability scans.
- DExecute Cross-Site Scripting (XSS) fuzzing scripts against database listening ports to assess input parameter sanitization.
Cevap
Implementing passive network traffic monitoring combined with offline static application security testing (SAST) provides comprehensive vulnerability visibility without sending active network probes, causing latency spikes, or triggering account lockouts on production services.
Combining passive network monitoring with static application security testing (SAST) provides effective vulnerability identification while adhering to strict non-intrusive operational boundaries. Passive scanning inspects network traffic out-of-band without injecting packets or performing authentication attempts, eliminating account lockouts and server latency. SAST inspects source code directly without requiring execution in a live production environment.
Adım Adım Çözüm
Anahtar Kavram
Passive Vulnerability Assessment and Static Testing Methods