Cyver Core imports ZAP web application scan results and vulnerability findings via XML. This includes scan results from the open-source scanner as well as from ZAP marketplace add-ons. Simply export to XML and Cyver Core will do the rest.
If you're using ZAP to automate your security scanning, you can also automatically import those scan results to Cyver Core with the API.
Findings Field Mapping
| Field | Values | Example |
| Code | default: auto-generated | |
| Title | { "alertitem": { <name>Strict-Transport-Security Header Not Set</name> } } | |
| Type | Vulnerability Observation | |
| Assets | ||
| Description | { "alertitem": { "desc": "HTTP Strict Transport Security (HSTS) is a web security policy mechanism whereby a web server declares that complying user agents (such as a web browser) are to interact with it using only secure HTTPS connections (i.e. HTTP layered over TLS/SSL). HSTS is an IETF standards track protocol and is specified in RFC 6797." } } | |
| Occurrence | ||
| Labels | ||
| Severity | Info Low Medium High Critical default: Info | <alertitem> <riskcode>2</riskcode> </alertitem> |
| CVSS20Score | ||
| CVSS20Vector | ||
| CVSS30Score | ||
| CVSS30Vector | ||
| CVSS31Score | ||
| CVSS31Vector | ||
| CVSS40Score | ||
| CVSS40Vector | ||
| Impact | 0 1 2 3 4 5 default: 0 | |
| ImpactDescription | ||
| Likelihood | 0 1 2 3 4 5 default: 0 | |
| LikelihoodDescription | ||
| VulnerabilityTypes | DoS CodeExecution Overflow MemoryCorruption SqlInjection XSS DirectoryTraversal HttpResponseSplitting BypassSomething GainInformation GainPrivileges CSRF FileInclusion | |
| CWEList | for example: CWE-1; CWE-721 | |
| CVEList | for example: CVE-1; CVE-721 | |
| MITRE ATT&CK Techniques | ||
| MITRE ATT&CK Mitigations | ||
| MITRE ATT&CK Tactics | ||
| Controls | ||
| Compliance Status | ||
| Compliance Comment | ||
| BackgroundInformation | ||
| Recommendation | { "alertitem": { "solution": "Ensure that your web server, application server, load balancer, etc. is configured to enforce Strict-Transport-Security." } } | |
| External References | { "alertitem": { "reference": [ "https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Strict_Transport_Security_Cheat_Sheet.html", "https://owasp.org/www-community/Security_Headers", "http://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security", "http://caniuse.com/stricttransportsecurity", "http://tools.ietf.org/html/rfc6797" ] } } | |
| Status | Draft PendingFix Fixed ReadyRetest Accepted ToReview Reviewed default: Draft | |
| Evidence Title | { "alertitem": { "instances": { "instance": { "uri": "https://private.canadianshield.cira.ca/dns-query" } } } } | |
| Evidence Location | ||
| Evidence Version | ||
| Evidence Reproduction | { "alertitem": { "requestheader": "POST https://private.canadianshield.cira.ca/dns-query HTTP/1.1 ..." } } | |
| Evidence Results | { "alertitem": { "responseheader": "HTTP/1.1 200 OK ..." } } | |
| Evidence Issue Details | <alertitem> </evidence> </instance> </instances> </alertitem> | |
Important Notes & Limitations
- The maximum number of findings that can be imported in a single upload is 5,000 findings.
- If your file exceeds this limit, the import may fail depending on the selected import options (e.g., aggregation settings or filtering by severity).