feat: adding Rafiki's First Security Audit blog post #95
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mkurapov
changed the title
BlairCurrey
reviewed
Oct 23, 2024
|
|
||
| At the beginning of the year, we were in contact with a security and penetration testing company to do an audit of Rafiki. Even though the software is still in its early stages, it is essential to gather feedback early to build a strong foundation for the software's security. The primary goals of the assessment were to evaluate several Rafiki components: the GraphQL Admin APIs, the frontend Admin UI component, as well as our underlying ILPv4 protocol. | ||
|
|
||
| The assessment was done using Rafiki’s local playground, based on the Open Source Security Testing Methodology Manual (OSSTMM) and Open Source Web Application Security Project (OWASP) methodologies. Given all of the source code for Rafiki and the local playground is readily available, this was deemed as a “crystal-box” test, meaning all of the source code, endpoints, architecture, etc. was known in-advance to the testers. |
There was a problem hiding this comment.
maybe add links for OSSTMM and OWASP and "crystal -box"?
There was a problem hiding this comment.
edited the section a bit, removed reference to crystal box since it didn't really involve the testers going deep into the code and testing branching logic etc
BlairCurrey
reviewed
Oct 23, 2024
BlairCurrey
reviewed
Oct 23, 2024
BlairCurrey
reviewed
Oct 23, 2024
BlairCurrey
reviewed
Oct 23, 2024
BlairCurrey
approved these changes
Oct 23, 2024
mkurapov
force-pushed
the
mk/rafikis-first-security-audit
branch
from
e0af7bf
to
462c944
Compare
mkurapov
force-pushed
the
mk/rafikis-first-security-audit
branch
from
462c944
to
120ef7c
Compare
mkurapov
force-pushed
the
mk/rafikis-first-security-audit
branch
from
7cffe45
to
efc03fe
Compare
| - audit | ||
| --- | ||
|
|
||
| At the beginning of the year, we were in contact with a security and penetration testing company to do an audit of Rafiki. Even though the software is still in its early stages, it is essential to gather feedback early to build a strong foundation for the software's security. The primary goals of the assessment were to evaluate several Rafiki components: the GraphQL Admin APIs, the frontend Admin UI component, as well as our underlying [ILPv4 protocol](https://interledger.org/developers/get-started/). The assessment was done using Rafiki’s local playground, based on the [Open Source Security Testing Methodology Manual (OSSTMM)](https://www.isecom.org/research.html) and [Open Source Web Application Security Project (OWASP)](https://owasp.org/) methodologies. |
There was a problem hiding this comment.
Didn't we also get our Open Payments implementation tested or did that happen afterwards?
JoblersTune
reviewed
Oct 25, 2024
JoblersTune
reviewed
Oct 25, 2024
JoblersTune
reviewed
Oct 25, 2024
|
|
||
| At the beginning of the year, we were in contact with a security and penetration testing company to do an audit of Rafiki. Even though the software is still in its early stages, it is essential to gather feedback early to build a strong foundation for the software's security. The primary goals of the assessment were to evaluate several Rafiki components: the GraphQL Admin APIs, the frontend Admin UI component, as well as our underlying [ILPv4 protocol](https://interledger.org/developers/get-started/). The assessment was done using Rafiki’s local playground, based on the [Open Source Security Testing Methodology Manual (OSSTMM)](https://www.isecom.org/research.html) and [Open Source Web Application Security Project (OWASP)](https://owasp.org/) methodologies. | ||
|
|
||
|  |
There was a problem hiding this comment.
You should update the alt text here 😉
sabineschaller
approved these changes
Oct 25, 2024
njlie
approved these changes
Oct 25, 2024
|  | ||
|
|
||
| The audit presented eight vulnerabilities in total. However, two items were not applicable to us: | ||
| Two items were not applicable to us: |
There was a problem hiding this comment.
extreme nit: "two of the eight items..." might be good to reinforce the context of what the reader is looking at but it's not blocking to me
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
Adds blog post for Rafiki's security audit.
Original draft.