Red team tool security evaluation
Agent Security Audit Checklist
A gated interactive checklist designed to guide red team leads through an agent security audit of penetration testing and offensive security tools. Covers agent architecture, communication channels, credential management, and operational security considerations.
Red teams deploying agents on target endpoints face a variety of security risks that can impact team effectiveness and client safety. This interactive checklist helps platform engineering and security leads systematically review agent security controls across common risk vectors.
The tool focuses on elements critical for agent security posture, including host-based protections, communication encryption, credential handling, and operational hygiene. Completing this checklist supports risk mitigation before field deployment.
Inputs
How is the agent installed on target systems? Choose the primary installation vector.
Select the primary communication method the agent uses to interact with command-and-control servers.
How does the agent store credentials for authentication to targets or servers?
What method does the agent use to maintain persistence on target devices?
Result
agent_installation_method == 'manual' ? 2 : 0 + communication_channel == 'unencrypted' ? 5 : 0 + credential_storage_method == 'plaintext' ? 7 : 0 + agent_persistence_mechanism == 'memory_only' ? 1 : 0 + agent_code_audited == 'no' ? 5 : 0 + data_exfiltration_controls == 'no' ? 5 : 0 + agent_uninstall_capability == 'no' ? 3 : 0Agent Security Assessment
Your agent's security posture indicates controlled risk, with adequate encryption and credential safeguards.
Best practice
Vendors should provide agents with encrypted communications (e.g., TLS 1.3), ephemeral credential handling, audited codebases, and documented uninstall procedures to minimize operational risk.
Subsequent sections unlock after submit