Documentation
Integrations: overview and permissions model
What REAP reads, what it writes, and the least-privilege permissions it asks for.
Principles
- Read-only integration users wherever REAP only reads.
- Writes are limited to the fields REAP populates: work notes, evidence links and custom fields you agree (verdict fields are in development).
- Every integration call is logged; credentials for integrations are stored encrypted and rotatable.
- Integrations are scoped in week 0 and verified in week 1 (Network Context Report).
Read / write matrix
| System | Reads | Writes | Product status |
|---|---|---|---|
| ServiceNow (opens in a new tab) | Incidents, problems, changes, CMDB (optional) | Investigation Window and evidence links to work notes; change-verification evidence as a work note (verdict fields in development) | Available |
| Jira (opens in a new tab) | Issues, change requests | Comments with evidence (verdict fields in development) | Available |
| ManageEngine ServiceDesk Plus | Tickets, CMDB records | Available | |
| CyberArk (opens in a new tab) | Credentials at time of use | — | Available |
| HashiCorp Vault (opens in a new tab) | Credentials at time of use | — | Planned · not available today |
| SolarWinds (opens in a new tab) · Zabbix (opens in a new tab) | Alerts, metrics, device lists | — (REAP does not modify monitoring) | Planned · today, incidents they raise reach REAP through ServiceNow (opens in a new tab) or Jira (opens in a new tab) |
| PagerDuty (opens in a new tab) · Opsgenie (opens in a new tab) | Incidents and on-call schedule | Investigation summaries | Planned · today via ServiceNow (opens in a new tab), Slack (opens in a new tab) or Teams |
| Slack (opens in a new tab) · Microsoft Teams (opens in a new tab) | Approval responses (where in-chat approvals are confirmed) | Summaries and runbook results | Available · in-chat approvals confirmed per pilot |
| Runbooks and documents (files, agreed exports) | Runbooks, designs, conventions | — | Available |
| Confluence (opens in a new tab) · SharePoint (opens in a new tab) | Runbooks, designs, conventions | — | Planned · today the same documents arrive as files and agreed exports |
| NetBox (opens in a new tab) | Inventory, IPAM, sites | — | On request |
| Flow records (NetFlow or IPFIX exporters) | Flow metadata, where you configure exporters to the connector | — | Available · no payload inspection, no continuous packet capture |
| Okta (opens in a new tab) · Microsoft Entra ID (opens in a new tab) | SSO assertions, groups | — | Available |
| AWS (opens in a new tab) · Azure (opens in a new tab) · Mist AI (opens in a new tab) · Aruba Central (opens in a new tab) · Meraki (opens in a new tab) | Network context, controller inventory and events | — | Available · GCP (opens in a new tab) network discovery not available today |
| Network platforms (Cisco (opens in a new tab), Arista (opens in a new tab), Juniper (opens in a new tab), HPE Aruba (opens in a new tab), Palo Alto Networks (opens in a new tab)) | Configurations, state, telemetry | Approved runbooks only | Available |
| Fortinet (opens in a new tab) · SONiC (opens in a new tab) · others | Configurations, state, telemetry | Approved runbooks only | Confirmed per pilot against your platforms and versions |
How each integration page is organized
- Overview · Prerequisites · Permissions requested · Setup · What REAP reads · What REAP writes · Troubleshooting · Changelog
Last reviewed: October 7, 2026 (draft) · Owner: solutions engineering · Corrections: security@reapnet.ai