defectdojo / community-contribs Goto Github PK

Hi Everyone,

I realize this is probably the wrong place to make this suggestion, but we don't know where to find this information... There are no mailing lists to search or discuss issues, and searching the web turns up nearly no information. Even that Slack site provides no information when searching. This is an awful situation to put folks in.

Please provide a list of consultants who can assist in installing, configuring and integrating with DefectDojo. For integrating with DefectDojo, we would like someone experienced with Veracode. Other people will have other <fav tools>. We are happy to pay someone to help with the tasks.

Thanks in advance.

Hi.

I installed the application and the bank on the same server (Centos) and when starting the containers the initializer is unable to connect to the database.
I already tested the connection with psql and is connecting.

What can be this problem?

How to suppress a known issue in defectdojo?
For example If I am running an NMAP scan daily and i want to suppress 80 and 443 open port issues. Is there a way to do that automatically?

Hello Community

i try to deploy "Defectdojo" into Kubernetes , but i find a lot of issues that blocked me ; so if some one from the communit that do it before , thank you share with as the steps .

Thank you

Source: https://github.com/DefectDojo/django-DefectDojo

Legacy install option of setup.bash is now named legacy-setup.bash in both dev and master branches. If this cloudformation template is run as is it will fail to use legacy install.

Line 230 in defectdojo_ec2.yml

Needs to be changed from ./setup.bash -b to ./legacy-setup.bash -b

Hello and thank you for viewing this issue. I have corrected some minor issues with, and hardened the following CloudFormation template:

https://github.com/DefectDojo/Community-Contribs/blob/master/aws-deploy-cloudformation-fargate/aws-fargate.yml

I will PR the changes for community review. That said, after having resolved the following issue ...

https://github.com/DefectDojo/Community-Contribs/issues/27

... authenticating successfully to DefectDojo, and successfully updating a Product I attempted to update a Finding record and was met w/ the following error:

failed to resolve broker hostname

Exception Location: /usr/local/lib/python3.8/site-packages/kombu/connection.py, line 451, in _reraise_as_library_errors
Python Executable: /usr/local/bin/uwsgi
Python Version: 3.8.12

OperationalError('failed to resolve broker hostname')
get_response <bound method BaseHandler._get_response of <<django.core.handlers.wsgi.WSGIHandler object at 0x7f2e3747c0a0>
request | <WSGIRequest: POST '/finding/128/edit'>

I noticed this issue

https://github.com/DefectDojo/django-DefectDojo/issues/1422

As I highly doubt the exception above is a bug, per-se, what I am wondering is if perhaps there is a misconfiguration in the CloudFormation template I am missing.

New syntax needs to be identified and tested.

Will create pull request at a later time.

Hello, and thank you for putting together this Fargate stack. I have spent some time w/ it and have made the necessary substitutions required to properly execute the template and successfully create the stack.

Problem: When I point my browser at the public IP on port 8080 and nginx handles my request, I receive an Internal Server Error message. Upon further inspection, in the CloudWatch log group for the ecs/initializer I found the following error:

django.core.exceptions.ImproperlyConfigured: The SECRET_KEY setting must not be empty.

Potential Solution:

I believe the DD_SECRET_KEY, and perhaps even the DD_CREDENTIAL_AES_256_KEY environment variables are missing from the services/tasks that require it. Can you confirm as you find time?

Hello.

Using deploy in CentOS can I use authentication via SAML2?

I followed this link https://github.com/DefectDojo/Community-Contribs/tree/master/CentOS-7-deploy

How do I enable this in my containers without losing configuration when restarting the service?