1) Data foundation
- • Publicly reachable network and HTTP signals.
- • Common exposure patterns (e.g. service exposure, header baselines).
- • Comparison against proven hardening baselines.
Transparency
Methodology: How ClawGuru evaluates the Security Check
This page explains which publicly visible signals we use, how the Claw Score is derived, and where the limits of a fast heuristic assessment are.
2) Scoring logic
The Claw Score is a heuristic prioritization: the lower the score, the more urgent the next hardening steps. The logic is optimized for rapid operational orientation, not final audit certainty.
3) Limits and risks
- • Not a replacement for penetration testing, code review, or internal architecture review.
- • Internal configurations without external visibility are not directly evaluated.
- • Recommendations should always be validated against logs, config, and change management.
4) Recommended workflow
- 1. Run a check and prioritize top risks.
- 2. Execute runbook fixes (quick wins first).
- 3. Validate internally (config, logs, monitoring).
- 4. Re-check and document progress.