docs: add the DevSecOps report #76
Merged
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
Signed-off-by: Mauran <[email protected]>
Kuruyia
commented
Feb 27, 2024
Kuruyia
commented
Feb 27, 2024
There was a problem hiding this comment.
I think the arrows should begin from the entity that initiates the connection.
Examples:
- Job service --> NATS (instead of Job service <-- NATS)
- Mobile app --> Keycloak (instead of Mobile app <-- Keycloak)
docs/devsecops/DevSecOps.tex
Outdated
| \hline | ||
| Backend pods & Man-in-the-middle & Privilege escalation & A man-in-the-middle attack is a form of cyberattack where an unauthorized third party intercepts and possibly alters communication between two parties without their knowledge or consent. & Since the API uses HTTPS, and if the machine of the user is not compromised, it is not possible to tamper with the traffic in a useful manner because it is encrypted. \\ | ||
| \hline | ||
| API Gateway & JWT spoofing & Spoofing & JWT spoofing is the deceptive practice of forging or altering JSON Web Tokens to impersonate legitimate users or gain unauthorized access to systems and resources. & Since our authentication token only lasts 5 minutes, we limit the time someone who stole a token can impersonate. \\ |
There was a problem hiding this comment.
I think this is the wrong mitigation explanation for this kind of attack:
Suggested change
| API Gateway & JWT spoofing & Spoofing & JWT spoofing is the deceptive practice of forging or altering JSON Web Tokens to impersonate legitimate users or gain unauthorized access to systems and resources. & Since our authentication token only lasts 5 minutes, we limit the time someone who stole a token can impersonate. \\ | |
| API Gateway & JWT spoofing & Spoofing & JWT spoofing is the deceptive practice of forging or altering JSON Web Tokens to impersonate legitimate users or gain unauthorized access to systems and resources. & Our OIDC access token is signed by Keycloak, and the API gateway checks that the signature is correct on the token provided by the user. Therefore, this kind of attack is not possible. \\ |
Signed-off-by: Mauran <[email protected]>
Signed-off-by: Mauran <[email protected]>
Kuruyia
added
documentation
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.
This adds the LaTeX report for the DevSecOps course.