search

praetorian-inc / chariot-ui

Chariot Offensive Security Platform
https://chariot.praetorian.com
MIT License
21 stars 6 forks source link

Standardize Risk Exports #756

Open Dan-Crawford opened 4 days ago

Dan-Crawford commented 4 days ago

Feature Description 1:1, or at least more parity between Risks page export and Org page export.

Problem Org page export has more useful information
Severity codes are not customer-readable in current json export Protocol, host, port, path are not available in json export Org page export has larger number of risks (risks are duplicated if on multiple ports [eg 80 and 443])

Description, impact, recommendations, identifiers are not in json export (empty in org export example I have)

Preferred Solution Present severity in customer-readable format Add protocol, host, port, path to json

Alternatives Considered As we role into more comprehensive reporting, the way risks are presented and exported will be changing. A more comprehensive risks page export may naturally solve these issues.

privateducky commented 3 days ago

To complete this one, we'll want to see a JSON proposal of the properties we'd like to include. @Dan-Crawford can you work with all stakeholders to create this?