![phoenix](https://d1a29h5kxv3oc2.cloudfront.net/dist/img/phoenix.81914efc7207f6a059bd10f5d3fd5f89.png)
Remove vulnerability by disabling SSL 2.0/3.0 and use TLS 1.2.
- or -
Post a project like this- Posted:
- Proposals: 10
- Remote
- #4165804
- Expired
![Top Endorsed Top Endorsed](https://dw3i9sxi97owk.cloudfront.net/uploads/prizes/badges/ffdd1b856a16c89191f1150e4430076b.png)
![Top Seller with earnings over £100k Top Seller with earnings over £100k](https://dw3i9sxi97owk.cloudfront.net/uploads/prizes/badges/6848fd9e0514ae9277cce59806b79dc5.png)
![Top Endorsed Top Endorsed](https://dw3i9sxi97owk.cloudfront.net/uploads/prizes/badges/ffdd1b856a16c89191f1150e4430076b.png)
![Babar A.](https://dw3i9sxi97owk.cloudfront.net/uploads/thumbs/4bb17a285b3d03e94229aaedf5bc16fb_70x70.jpg)
![Awais A.](https://dw3i9sxi97owk.cloudfront.net/uploads/thumbs/a4e41b9f85800e340239360ea587c485_70x70.png)
![Sagar B.](https://dw3i9sxi97owk.cloudfront.net/uploads/thumbs/b5ff4ffaa98b3a88590018f54374dd70_70x70.jpg)
![Shreef E.](https://dw3i9sxi97owk.cloudfront.net/uploads/thumbs/ea40eb7c65c8b99a509b24addc7cf03c_70x70.jpeg)
![Tefoor A.](https://dw3i9sxi97owk.cloudfront.net/uploads/thumbs/471890689bfa82f07facb79c095337f4_70x70.png)
Description
This project aims to enhance security on a legacy Linux server by disabling outdated and vulnerable SSL/TLS protocols and implementing more robust encryption standards. Due to the sensitive nature of the systems involved, testing must be done in an isolated lab environment that replicates the production server configuration.
The initial vulnerability assessment found the server permits connections using SSL 2.0 and 3.0, protocols that are no longer considered secure. To strengthen protections, these will need to be disabled on the server configuration. Additionally, the assessment recommends migrating to TLS 1.2 as the minimum encryption standard, using cipher suites that provide adequate security.
The contractor's role will be to test the environment to mirror the production Linux server. Thorough testing is then required to validate all critical business services and applications continue running as expected with the proposed SSL/TLS changes implemented. Once verified, recommendations for applying the same upgrades to the live production server in a planned migration can be provided.
The overall goal is to bolster security by eliminating use of outdated and vulnerable protocols while ensuring minimum disruption to operations. Configuring the isolated lab system and thoroughly verifying compatibility and operations across applications is key before any changes go live.
![Wayne H.](https://www.peopleperhour.com/imgs/default_avatar_light_70x70.png)
Wayne H.
97% (29)New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-
HI,
What Linux version and application are running on the server?
If you look at the following time line, TLS 1.3 would be the ideal one to migrate (considering all applications are supported the TLS 1.3)
SSL 1.0: Security vulnerabilities prevented its release to the public.
SSL 2.0: Launched in 1995 but has known problems with security. It was deprecated in 2011.
SSL 3.0: Launched in 1996 but deprecated in 2015. Known to have security flaws.
TLS 1.0: Released as an SSL 3.0 upgrade in 1999 and deprecated in 2021.
TLS 1.1: Launched in 2006 and deprecated in 2021.
TLS 1.2: Launched in 2008.
TLS 1.3: Launched in 2018.
Please feel free to revert !
-
1. What webserver are you running?
2. What Version of the web server software are you running
3. What applications are you running on the server, and what technologies/frameworks do you use? -
What is the Web-Server, Apache or Nginx?
-
Hello Wayne,
Please confirm that you would be providing the isolated testing server (as opposed to the contractor, who would not have your application software).
Regards,
John R