Website security corrections

Job ID: 35177347

Budget: €30 – €250 EUR

We have a project that has a security report and needs correction
The findings were identified by the security rating agency BitSight.

The client domain in this text changed to "clientdomain.com" for privacy reasons, we will give the correct domain to the chosen freelancer.

1
Risk Vector,Finding Identifier,Attributed To,Details,Remediation Instructions,Comments,Destination Port,Certificate Issuer,Certificate Subject,Certificate Subject Alternate,Certificate Serial Number,Observed IPs,Belongs to service provider?,Diffie-Hellman Prime Name,Diffie-Hellman Prime Length,Diffie-Hellman Prime,Product,Transport Method,Final Location,Cache-Control,Content-Security-Policy,X-Content-Type-Options,Strict-Transport-Security

2
Web Application Headers,clientdomain.com:443,MEAG Munich Ergo Asset Management GmbH,Ineffective headers: Set-Cookie

3
SSL Configurations,clientdomain.com:443,MEAG Munich Ergo Asset Management GmbH,Diffie-Hellman prime is very commonly used and is not safe,"(Diffie-Hellman prime is very commonly used and is not safe) A common Diffie-Hellman prime indicates poor server-side TLS configuration

4
Web Application Headers,premiumespaco.com:80,MEAG Munich Ergo Asset Management GmbH,Missing required headers,"(Missing required headers) One or more required security headers are not set. - Ensure your policy correctly implements the required headers. Refer to the <a target=""new"" href=""https://help.bitsighttech.com/hc/en-us/articles/360008632054"">list of required headers</a>.",,80,,,,,clientdomain.com[85.XX.135.129]:80,,,,,,,http://clientdomain.com/,No Issues,Missing required headers,Missing required headers,No Issues

5.
Web Application Headers,www.clientdomain.com:443,MEAG Munich Ergo Asset Management GmbH,Ineffective headers: Set-Cookie

6
SSL Configurations,www.clientdomain.com:443,MEAG Munich Ergo Asset Management GmbH,Diffie-Hellman prime is very commonly used and is not safe,"(Diffie-Hellman prime is very commonly used and is not safe) A common Diffie-Hellman prime indicates poor server-side TLS configuration