[routing-wg] Code Audit Report for RPKI

Dear Job,

Thanks for taking interest.

> On Dec 9, 2021, at 3:46 PM, Job Snijders <job at fastly.com> wrote:
> 
> Thank you for sharing this. Both the audit report and the response to
> the audit report seemed comprehensive and informative.
> 
> Out of curiosity, will RIPE NCC employ a different (new) auditor in
> 2022? Periodically changing auditors can potentially help increase the
> diversity in terms of perspective on code and security. Each auditor
> represents 'fresh eyes', a useful characteristic when dealing with
> complex systems.

We agree on this.

Preliminary to making an audit, we select an auditing company that best matches
our criteria for the specific audit. In 2021, we found that Radically Open
Security best fit our requirements for our needed audits. In 2020, we had
penetration tests done by a different auditing company.

Through this exercise, we also found that not all auditors allow the publication
of the results. Since this is something we value, we will continue to select
auditors that allow us to make the results publicly available. Having different
perspectives is another important criterion, so we'll make sure we explore other
vendors during the selection process.

Hope this helps.

Kind regards, 
Bart Bakker
RIPE NCC