Sonatype Nexus Lifecycle Undesirable Blockage

Does this solution block undesirable open source components from entering your development lifecycle? If yes, how?

EdwinKwan
Security Team Lead at Tyro Payments Limited
The solution blocks undesirable open-source components from entering our development lifecycle, based on the policies that we set. It will break the bill straight away. There's no way you can ship code that introduces new vulnerabilities. We just don't allow it at all.
View full review »
Gus Orologas
Lead IT Security Architect at a transportation company with 10,001+ employees
It also blocks undesirable open-source components from entering our development lifecycle. It scans code libraries and it flags them if there's a vulnerable version. It shows us very quickly if there is a newer version available, and what generation that non-vulnerable version is.
View full review »
Russell Webster
VP and Sr. Manager at a financial services firm with 1,001-5,000 employees
The solution blocks undesirable open-source components from entering our development lifecycle. That's its whole point and it does it very well.
View full review »
JavaDevef0ca
Java Development Manager at a government with 10,001+ employees
The solution blocks undesirable open-source components from entering our development lifecycle. There are certain .jars which we can block.
View full review »
ConfigManag73548
Configuration Manager at a health, wellness and fitness company with 5,001-10,000 employees
There are a number of open-source components that it has highlighted. It means that we have to find a replacement for them. There's a recommendation that's given when it highlights them. So we can remain in the same open-source components, it's just that there has been a patch or an update to them to close off vulnerabilities.
View full review »
Sign Up with Email