Automate Your Entire Offensive Security Workflow

Connect AttackForge to everything. Trigger actions on events. Eliminate manual handoffs.

Flows is the automation engine that turns your pentest data into action automatically.

Manual Handoffs Are Killing Your Security Program

Every time a pentester finds a vulnerability, a cascade of manual work begins.

Copy-paste. Email. Update spreadsheet. Create ticket. Notify stakeholder. Repeat forever.

Findings Never Make It to Tickets

Pentesters find critical vulnerabilities. Customers wait for the report to be delivered. Findings sit in a report while someone manually creates Jira tickets if they remember at all.

Stakeholders Are Always Surprised

Dev teams find out about vulnerabilities days or weeks later. No real-time notifications. No automated escalations. No accountability.

Your Tools Don't Talk to Each Other

AttackForge. Jira. ServiceNow. Slack. Power BI. Tenable. Each one is an island. You're the bridge and it's exhausting.

Can't Prove What Happened When

Auditors ask for evidence of your vulnerability management process. You scramble to reconstruct timelines and recover evidence from email threads and memory.

Every Tester Does It Differently

One pentester says fix it this way. Another pentester says fix it that way. Devs have no idea who to trust. Zero standardization.

30-40% of Time Spent on Non-Testing Work

Your expensive security professionals spend nearly half their time on administrative tasks instead of finding vulnerabilities.

Meet Flows: Your Automation Command Center

Flows is AttackForge's built-in automation engine powered by AFScript.

Connect AttackForge to any system with an API. Trigger actions on events.

Build complex workflows with conditional logic. No external automation tools required.

Trigger on Any Event

Start automations when vulnerabilities are created, projects update, retests complete, or any of 30+ internal events. External webhooks supported too.

• Internal Events e.g. Vulnerability Created/Updated
• Create your own APIs and trigger them from your other systems and scripts
• Use Actions to trigger user-driven automations in the UI via button-clicks
• Scheduled (Time-Based) Automations
• Custom HTTP Webhooks

Chain Unlimited Actions

Build multi-step workflows with HTTP requests, conditional logic, loops, and data transformation. Actions execute in sequence with full error handling.

• HTTP Actions (GET, POST, PUT, PATCH, DELETE)
• Script Actions (custom AFScript logic)
• Conditional branching & loops
• Secrets management & logging

Connect to Anything

If it has an API, Flows can connect to it. Jira, ServiceNow, Slack, Teams, Power BI, Tenable, Qualys and your custom tools.

No-Code to Pro-Code

Start simple with pre-existing library of open-source Flows. Add custom logic with AFScript when you need more power. Export and share flows with your team.

Scheduled Automations

Run automations on a schedule - daily SLA checks, weekly reports, monthly scans.

Secure by Design

Encrypted secrets management. RBAC for flows. Audit trails for every run.

Flows is Included

No external tools to manage. One platform for offensive security management AND automation.

Build Automations in Minutes, Not Months

Choose Your Trigger

Select what starts your automation:

• Internal Event (vulnerability created, etc.)
• External Webhook (from other systems)
• Scheduled Time (daily, weekly, custom)
• Actions (from users clicking buttons)

Build Your Actions

Chain together actions that execute in sequence:

• HTTP Requests to any API endpoint
• Script Actions for custom logic
• Conditional branching (if/then/else)
• Loops for batch processing

Test & Debug

Run your flow manually with test data:

• See request/response for each action
• View detailed logs and stack traces
• Iterate quickly without waiting

Enable & Monitor

Flip the switch and watch it run:

• Real-time run history
• Success/failure status
• Re-run failed flows with one click
• Full audit trail for compliance

Integrate with the Tools You Already Use

Flows connects AttackForge to your entire security and IT ecosystem.

Ticketing & Project Management

• Jira

• ServiceNow

• Azure DevOps

• Auto-create tickets when vulnerabilities are found

• Bi-directional sync of notes, files, data

• Assign tickets based on asset ownership

• Escalate overdue vulnerabilities

Collaboration & Notifications

• Slack

• Microsoft Teams

• Email

• Real-time alerts for critical findings

• Daily/weekly vulnerability digests

• Escalation notifications for SLA breaches

• Project status updates to stakeholders

Security Tools

• Tenable

• Rapid7

• Qualys

• HackerOne

• Bugcrowd

• Import findings from scanner tools

• Trigger scans based on project events

• Sync bug bounty submissions

• Correlate with threat intelligence (VulnDB)

GRC & Compliance

• RSA Archer

• MetricStream

• OneTrust

• LogicGate

• Feed vulnerability data to risk platforms

• Automate compliance evidence collection

• Track remediation against policies

• Generate audit-ready reports

Business Intelligence

• Power BI

• Tableau

• Export pentest metrics to dashboards

• Visualize vulnerability trends

• Executive reporting automation

• Custom KPI tracking

Custom & Internal Tools

• Custom APIs

• Internal Systems

• Connect to internal CMDBs

• Integrate with custom ticketing systems

• Feed data to homegrown dashboards

• Webhook to any HTTP endpoint

Pre-Built Flows to Get You Started

Don't start from scratch. Import these battle-tested flows and customize for your environment.

Vulnerability → Jira Ticket

Trigger: Vulnerability Created

SLA Breach Escalation

Trigger: Scheduled (Daily at 9am)

Bug Bounty Ingest

Trigger: HTTP Webhook from HackerOne

Executive Weekly Report

Trigger: Scheduled (Monday 8am)

Remediation Verification

Trigger: Vulnerability Updated (Status = "Fixed")

Asset-Based Routing

Trigger: Vulnerability Created

AFScript: When Visual Isn't Enough

Need custom logic? AFScript is AttackForge's built-in scripting language that gives you full programmatic control over your automations. Transform data, implement conditional logic, handle errors gracefully, and build exactly what you need.

// Example: Route vulnerability to team based on severity
const vuln = data.vulnerability;
const severity = vuln.severity;

let team = "security-general";
let priority = "Medium";

if (severity === "Critical" || severity === "High") {
  team = "security-urgent";
  priority = "High";
  Logger.info(`Critical/High finding – routing to urgent queue`);
}

if (vuln.cvss >= 9.0) {
  // Escalate to CISO for CVSS 9+
  team = "ciso-direct";
  Logger.warn('CVSS ' + vuln.cvss + ' – escalating to CISO');
}

return {
  decision: { status: "continue" },
  request: {
    body: {
      project: vuln.project_id,
      assignee_team: team,
      priority: priority,
      title: vuln.title
    }
  },
  data: { team: team, priority: priority, vuln_id: vuln.id }
};

AFScript Capabilities

• Full JavaScript-like syntax
• Access to trigger event data
• Transform request/response payloads
• Conditional logic and loops
• Secrets management integration
• Comprehensive logging
• Error handling with stack traces

Automation with Governance

Flows isn't just powerful - it's enterprise-ready with the security, access control, and audit capabilities large organizations require.

Role-Based Access Control

Control who can create, view, edit, or trigger flows. Share flows with teams while protecting sensitive integrations.

Access Levels: None, Info, View, Edit, Trigger

Secrets Management

Store API keys, passwords, and tokens securely. Reference secrets in flows without exposing values. Rotate credentials without updating flows.

Complete Audit Trail

Every flow run is logged with full details - input data, actions taken, responses received, duration, and outcome. Prove what happened when.

Header Redaction

Prevent sensitive headers from being logged or visible to flow editors. Whitelist or blacklist headers for security.

Flow Transfer

Transfer flow ownership when team members change roles. Maintain continuity without rebuilding automations.

Import/Export

Export flows to share with other teams or backup configurations. Import pre-built flows to accelerate deployment.

Why Flows Instead of Zapier/n8n/Power Automate?

You could use external automation tools. But here's why Flows is purpose-built for security workflows.

Flows is Included

Flows is included in AttackForge Enterprise and Core SME plans. No additional subscriptions. No external tools to manage. One platform for offensive security management AND automation.

Frequently Asked Questions

Do I need to know how to code to use Flows?

No. You can build useful automations using pre-built templates without writing any code. AFScript is available when you need custom logic, but it's optional.

What systems can Flows connect to?

Any system with an HTTP interface. This includes Jira, ServiceNow, Slack, Teams, Tenable, Qualys, Power BI, and thousands more. If it has an API endpoint, Flows can talk to it.

Is Flows secure for enterprise use?

Yes. Flows includes encrypted secrets management, role-based access control, header redaction, and complete audit trails.

Can I trigger Flows from external systems?

Yes. HTTP Triggers allow external systems to send webhooks to AttackForge and trigger your flows. You can configure authentication requirements and header restrictions.

How many Flows can I create?

There's no limit on the number of Flows you can create. Build as many automations as your workflows require.

Can I share Flows with my team?

Yes. Flow owners can share access with other users at different permission levels (Info, View, Edit, Trigger). You can also export flows to share as files.

What happens if a Flow fails?

Failed flows are logged with full details including error messages and stack traces. You can re-run failed flows with one click, or modify and test before re-enabling.

Is Flows available for self-hosted deployments?

Yes. Flows is available in both cloud and self-hosted AttackForge Enterprise deployments.

Implementation Maturity Journey

Proven roadmap from first automation to full workflow orchestration

Foundation

Week 1–2

• Connect AttackForge to your ticketing system
• Set up first event-driven Flow
• Configure secrets vault for API keys
• Deploy pre-built notification Flows

Expansion

Week 3–6

• Build multi-step Flows with conditional logic
• Integrate additional tools (Slack, Teams, SIEM)
• Implement SLA monitoring automations
• Enable scheduled Flows for reporting

Orchestration

Month 2–3

• Chain Flows across the full vulnerability lifecycle
• Implement AFScript for custom data transformations
• Automate executive reporting cadence
• Set up cross-project automation patterns

Optimization

Ongoing

• Benchmark automation coverage metrics
• Optimize Flow performance and error handling
• Share proven Flows across teams via export/import
• Leverage HTTP Triggers for external orchestration

Stop Copy-Pasting. Start Automating.

Every minute your team spends on manual data entry is a minute not spent finding vulnerabilities.

Flows eliminates the busywork so your security team can focus on what matters.