Finding write-up drafting

Security Reporter documents the findings from a penetration test so a team can act on them. A Beam agent reads new findings the connector exposes, applies your rule for wording, severity, and required fields, and drafts a clean write-up for each one. It fills the standard sections and attaches evidence where present. Findings that are ambiguous, touch a critical system, or lack proof are held for a tester to write up themselves. Routine, well-evidenced findings are drafted on their own, so testers spend their time probing systems rather than typing up every result by hand.

Report assembly and delivery

Security Reporter gathers findings into a report a client or stakeholder receives. A Beam agent reads the findings marked ready, applies your rule for which belong in a given report and in what order, and assembles the document from your template. It records who the report is for and when it was prepared. Reports covering sensitive engagements, or containing unresolved critical findings, are routed to a lead to approve before anything leaves. Routine reports are compiled and queued on their own, so the team delivers consistent documents without rebuilding each one from scratch every engagement.

Severity and status tracking

Security Reporter records the severity and remediation status of each finding over an engagement. A Beam agent reads status updates as fixes land or retests happen, applies your rule for how each maps to a state, and updates the finding to show it open, retested, or closed. It dates the change and notes who reported it. Findings that reopen, escalate in severity, or stall past a set date are flagged for a person to chase. Routine status upkeep happens as updates arrive, so the report reflects real progress without someone editing each finding by hand.