detections tracked
6 open · 0 in the last 24h
AI-driven Orchestration via API and Playbooks
API Radar unifies telemetry across ADC and edge security platforms, including F5 BIG-IP, Cloudflare, A10 Networks, and Citrix NetScaler, to detect emerging threats, identify the safest and most effective mitigations, and execute approved responses with a second operator's authorization.
Detect, decide, and defend from one command deck, across vendors, instead of juggling six consoles.
6 detections in 12h
hover a blip or a legend row
ring · type
colour · actor
angle = age · newest at the top
estate overview · aggregate
auto-refresh every 8s
detections tracked
6 open · 0 in the last 24h
devices under watch
2 online · 1 degraded · 0 live-enabled
approved playbooks
rest and ansible runbooks cleared for use
mitigations executed
0 succeeded · 0 awaiting approval
severity mix
6 detectedsignals · last 12h
0 eventslive activity
sync 14:07run it now
These are the two moves you make in the console. One ends an incident that is happening now, the other makes the next one a single click.
Pick the target device and the recommended preset, dry-run the exact iControl REST payload, then release it to the BIG-IP once a second operator approves.
Author a REST mitigation or paste an Ansible runbook, set the risk level, and it becomes available in the launcher for every approved operator.
the gap
Three consoles, one clock, and no shared record of what was decided.
signal
01DoS vectors in one console, WAF signatures in another, LTM counters in a third. Nobody correlates them under pressure.
time
02By the time a runbook is reviewed and a change window opens, the traffic profile has already moved.
trust
03Full auto-mitigation is a career risk. Manual mitigation is a latency risk. Teams end up doing neither well.
how it works
The same three tiles you operate in the console, from the first signal to the signed change.
Telemetry from BIG-IP ASM, DoS, LTM and APM is correlated into a single detection: severity, indicators, the vector and the exact device it touched.
A decision engine reads the detection and returns the likely attack, the blast radius, the rollback path and one recommended preset. Confidence is stated, not implied.
Dry-run the payload first. Release the change to the device only after a second operator approves. Every request, response and approval is written to the ledger.
▍ Works with the BIG-IP you already run. iControl REST for direct changes, Ansible runbooks when your change control lives in a pipeline. Nothing is rewritten, nothing is replaced.
capabilities
Each contract carries an entitlement. Owners and leads then decide which of these capabilities each member gets, so a NOC analyst and a change approver see different surfaces of the same platform.
Live radar, telemetry rail and the defense launcher.
Correlated detections with AI decision analysis.
BIG-IP inventory and iControl connection settings.
REST and Ansible mitigation definitions.
Run ledger, approvals and rollback records.
Release an approved change to a device.
access model
Registering an account does not open the product. Every registration is reviewed, tied to a contract, and granted a role. Nothing past the login is reachable until that approval lands.
Owns the commercial relationship and the membership list. Can add or remove members and assign leads.
Runs the security operation. Approves registrations and decides which capabilities each member is trusted with.
Sees only the capabilities shared with them. A detection analyst does not automatically get change approval.
Immutable product owner. The founding account is fixed in code and cannot be removed, demoted or re-scoped by any contract owner or app admin.
get more info
Send us the shape of your estate: how many BIG-IP devices, which modules, and who needs to see what. We will come back with a scoping call and the contract terms that fit.