Creating and Ingesting Records
Risks and incidents can enter the Adversarial platform along four paths. Whichever path a record takes, it lands in the same register, carries the same fields, and flows through the same scoring and reporting as every other record — the paths differ only in where the information starts and how much of it arrives at once.
| Method | Best for | Risks | Incidents |
|---|---|---|---|
| Manual entry | A single record you’re logging as you learn of it | Yes | Yes |
| CSV import | A one-time bulk load, such as migrating an existing register | Yes | Yes |
| Integration ingestion | Continuous, automatic intake from your security tools | Yes | Yes |
| AI document import | Extracting findings from a narrative report | Yes | — |
Manual Entry
Section titled “Manual Entry”Click Add Risk on the risk register or Add Incident on the incident register, and a new record appears at the top of the register ready to fill in. This is the right path for the record you’re creating as you learn of it — an employee report, a finding from a meeting, an incident phoned in.
See Creating Risks and Creating Incidents for the fields to populate.
CSV Import
Section titled “CSV Import”The dropdown next to the Add Risk / Add Incident button offers Import CSV for bulk creation. Each register provides a downloadable template with the expected headers and formats; fill it out, upload it, and the records are created in one pass. This is the usual path for migrating an existing risk register or incident log into the platform.
See the CSV field references in Creating Risks and Creating Incidents for formats and caveats — CSV values are case-sensitive and dates must be YYYY-MM-DD.
Integration Ingestion
Section titled “Integration Ingestion”Connected sources feed the registers continuously: findings from your scanners, bug bounty programs, and attack-surface tools arrive as risks, and detections from your security operations tools arrive as incidents — no manual action once the integration is configured. Each integration maps the source tool’s statuses, severities, and fields onto the platform’s, keeps records updated on re-sync, and can carry the source assignee over when it matches a member of your organization.
See Integrations for the available sources and each one’s setup guide and field mappings.
AI Document Import
Section titled “AI Document Import”Import via AI, in the risk register’s add menu, turns a narrative document — a pen-test report, an audit memo, a vendor assessment — into proposed risks. Upload a text, Markdown, PDF, or Word document; the AI proposes candidate risks, each shown side-by-side with the passage of the document it was drawn from; and only the proposals you approve are added to the register.
See Creating Risks for the workflow and AI Features for how the AI is used.
Your Own Automation
Section titled “Your Own Automation”Beyond the four built-in paths, anything that can call the platform’s API can create records: service accounts support scripted and scheduled automation, and an AI assistant connected over MCP can create and update records on your behalf, within the permissions you grant.