Findings
Each issue Hardpoint detects is reported as a finding with detailed information to help you understand and remediate the issue.Finding Structure
Severity Levels
| Level | Description | Action |
|---|---|---|
| Critical | Immediate security risk | Fix immediately |
| High | Significant security concern | Fix soon |
| Medium | Potential security issue | Review and fix |
| Low | Minor security consideration | Fix when convenient |
| Info | Informational finding | No action required |
Confidence Levels
| Level | Meaning |
|---|---|
| High | Very likely a real issue |
| Medium | Probably an issue, verify |
| Low | Might be a false positive |
Filtering Findings
By Severity
By Confidence
Combined Filters
Finding IDs
Each scanner uses a prefix for its finding IDs:| Prefix | Scanner |
|---|---|
AI- | AI Configuration |
SHELL- | Shell Configuration |
GIT- | Git Security |
NET- | Network Exposure |
SECRET- | Secrets |
Output Formats
Terminal
Human-readable output with colors and formatting:JSON
Machine-readable for scripting:SARIF
For GitHub Code Scanning and IDE integration:Remediation
Each finding includes remediation guidance. Common actions:| Finding Type | Typical Remediation |
|---|---|
| Instruction Override | Remove override attempts from config |
| Hidden Unicode | Use hardpoint fix AI-003 to strip |
| Curl Pipe Bash | Download then inspect before running |
| Exposed Service | Bind to 127.0.0.1 instead of 0.0.0.0 |
| Hardcoded Secret | Move to environment variables |
References
Many findings include references to:- Security advisories
- Best practice documentation
- Attack technique descriptions