-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set up vulnrelay (vulnerability scanning) #207
Conversation
89eb8c2
to
5dbb624
Compare
@@ -0,0 +1,5 @@ | |||
ENV=prod | |||
DD_URL= |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's add the default url here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think exposing urls of our infrastructure services in the open source repository is a good idea
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
okay maybe let's leave a hint where to look
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a link to the internal handbook in the README_AWS
@@ -0,0 +1,5 @@ | |||
ENV=prod |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is only used by the dsn, right? what's the idea here? to use the same dsn as the project? if so then the ENV should default to vulnrelay-prod
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The idea was to use the same sentry project for all servers, but use the environment field to differentiate between them.
And the environment is being constructed from DD_PRODUCT and ENV:
environment = f"{settings.DD_PRODUCT} - {settings.ENV}"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
using the same dsn for all project is a security risk. I'd rather have them separate, even if separated from the project's DSN
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't get it, how exactly are multiple sentry DSNs safer than a single one?
When it comes to various bugs that may arise in production, having all of them in a single place seems much more convenient to manage. Also, creating a separate sentry setup for each new project we ship can be daunting.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the security risk is: if one DSN gets compromised a malicious actor can spawn errors for all nodes, and cycling the DSN would require changing configs of all deployments. If creating projects is troubling then it is a problem we can solve with a steady supply of evaluation candidates - sentry API allows for creation of projects. It could be a part of CADM or whatever.
ENV=prod | ||
DD_URL= | ||
DD_API_KEY= | ||
DD_PRODUCT= |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is not explained, there should be a mention of the convention: product=client_server_group
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a good point, but I was thinking this should be somewhere in our internal handbook in the relevant section about vulnerabilities management. Here we just referring to whatever was created in DefectDojo. Wdyt?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure, leaving it in another place is gonna be gelpful, people will just forget about it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added some clarifying comments to the .env
file
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
posted some questions
4af8dc2
to
42d2c08
Compare
42d2c08
to
88300d2
Compare
No description provided.