Informix Security Review: Report Template
How the findings go to a customer.
The report leads with the risk verdict and the three to five fixes that remove most of it; the full findings table goes in the appendix.
- Executive summary (half a page). Overall rating (Critical / High / Medium / Low exposure), the top findings in one line each, and what fixing them removes. No Informix jargon.
- Scope and method. Instances, hosts, versions, dates, who ran the collector and as which user, what was out of scope.
- Findings by severity. One block per finding, Critical first:
| Field | Content |
|---|---|
| ID and title | e.g. PRIV-01 — PUBLIC holds DBA on database stores |
| Severity | Critical, with one-line justification if changed from default |
| Evidence | Exact row or command output from the bundle |
| Risk | Any user who can connect can drop or alter every table |
| Remediation | REVOKE DBA FROM PUBLIC; GRANT CONNECT TO PUBLIC; then role-based grants |
| Verification | Re-run ifx_secaudit.sh -d stores; PRIV-01 shows PASS |
- Remediation plan. Findings grouped into change windows: config-only (restart needed or not), privilege changes, upgrades.
- Appendix. Full
findings.csv, version matrix row for the customer's release, list of evidence files.
Part of the Informix Security Review set. Check IDs are the ones used in the findings file of the scripts.