Updated Documentation on Anchore Enterprise

[Sopuru]

Anchore Engine has reached end-of-life (EOL) and has been replaced by Anchore Enterprise. I have updated the documentation for the Anchore Enterprise Vulnerability Data Parser to reflect recent changes, as detailed in this PR: #12020.

For instance, Anchore-CLI has been replaced with anchorectl. The documentation previously referenced anchore-cli, which has now been corrected, along with an updated data sample.

[dryrunsecurity]

DryRun Security Summary

Documentation update for Anchore Enterprise vulnerability scanning reveals potential security risks through detailed vulnerability reporting, including information disclosure, timestamp exposure, and external link details.

Expand for full summary

Summary: Documentation update for Anchore Enterprise vulnerability scanning, providing more detailed guidance and example JSON structures for vulnerability reporting.

Security Findings:
• Information Disclosure Risks

• Sample JSON reveals specific CVE (CVE-2023-24531) with high CVSS score of 9.8
• Includes full binary path (/usr/local/bin/gosu)
• Exposes package and version details

• Timestamp Exposure

• Includes specific timestamps for vulnerability detection and fix observation
• Potential information leakage about scanning environment

• External Link Exposure

• Direct link to NVD vulnerability detail page (https://nvd.nist.gov/vuln/detail/CVE-2023-24531)
• Could provide additional vulnerability context

View PR in the DryRun Dashboard.

[Maffooch]

This is okay to stay against the master branch since it is docs only, but please update the entry in a way that aligns with #12020

[Maffooch]

It would be best to link to the unit test in the repo once it gets merged in

[Maffooch]

Both formats are still supported, so we do not want to the remove docs for the old version

[github-actions]

This pull request has conflicts, please resolve those before we can evaluate the pull request.

[Maffooch]

Got some conflicts on this one now

[valentijnscholten]

@Sopuru Could you look at resolving the conflicts? I see on master there is now also info about old format and new format. Not sure how that relates to the docs changes in this PR.