Type: Feature Request / Refactor
Implementation of Modular Fingerprinting Analyzers and Deep Scan Preset
Description
Instead of a monolithic deep_scan implementation, we propose a modular approach where specific reconnaissance tasks are implemented as independent analyzers. This allows for better testing, user granular control, and maintainable code.
Proposed Granular Options
DNS Recon (check_dns)
- Independent module to query MX, TXT, and SRV records
Dynamic DOM Analysis (render_js)
- Headless browser execution to find frameworks in the post-rendered DOM
Asset Analysis (analyze_assets)
- Deep inspection of CSS/JS bundles and CDN paths
Active Probing (active_probing)
- Requests for sensitive files (
.env, .git) and error page analysis
The Role of deep_scan
deep_scan will act as a configuration preset. When enabled via CLI (--deep-scan) or Config, it will act as a shortcut to enable all the above modules simultaneously.
Benefits
- Users can run
ciberwebscan analyze --dns without triggering a heavy headless browser
- Security audits can avoid
active_probing to stay within "Passive" engagement rules while still using render_js
Type: Feature Request / Refactor
Implementation of Modular Fingerprinting Analyzers and Deep Scan Preset
Description
Instead of a monolithic
deep_scanimplementation, we propose a modular approach where specific reconnaissance tasks are implemented as independent analyzers. This allows for better testing, user granular control, and maintainable code.Proposed Granular Options
DNS Recon (
check_dns)Dynamic DOM Analysis (
render_js)Asset Analysis (
analyze_assets)Active Probing (
active_probing).env,.git) and error page analysisThe Role of
deep_scandeep_scanwill act as a configuration preset. When enabled via CLI (--deep-scan) or Config, it will act as a shortcut to enable all the above modules simultaneously.Benefits
ciberwebscan analyze --dnswithout triggering a heavy headless browseractive_probingto stay within "Passive" engagement rules while still usingrender_js