Of course, if the company leadership doesn&#x27;t care, then you will have a hard time convincing them why the upfront effort of &quot;doing it right&quot; is worth it. When dealing with this situation, I found it useful to compare IT security people to lawyers. Wait, hear me out before you shout me down. :)<p>To the non-initiated, lawyers and infosec people are seen with nearly-equal amount of both dislike and trepidation. They are seen as a force of lawful evil that descends on your team and starts telling you that all those cool things you&#x27;re trying to do cannot actually be done, or must be done in a non-obvious roundabout way. When asked for reasons, both lawyers and infosec start talking about concepts that are entirely unfamiliar to most devs (code provenance, license agreements, trademarks, patent litigation, IP isolation, containers and namespaces, RBAC policies, multifactor authentication). All you care about is that this is a person who is telling you that your project, 99% complete after your team worked multiple 60-hour weeks, must be delayed until a bunch of things -- that you don&#x27;t consider broken! -- are fixed.<p>However, this is where things usually go differently. If a lawyer comes to management and says &quot;this project cannot launch because a bunch of code was copy-pasted from stackoverflow and links with an incompatibly-licensed library,&quot; the management is likely to listen even if they don&#x27;t understand a word of what was said -- because they know the importance of lawyers and know that, in the long run, litigation is extremely expensive. However, if an infosec person comes to them and says &quot;this project cannot launch because they have a PHP script running as root that listens on external port 80,&quot; management will not value this input nearly to the same degree, even though, in the long run, a bad security vulnerability can have just as much of a detrimental impact on a company as litigation -- and probably worse, because you won&#x27;t be able to hush-hush and &quot;settle out of court.&quot;<p>The reasons for this are multiple -- infosec is in infancy compared to the legal field, and, sadly, many IT security practitioners tend to look and act in a way that makes their recommendations carry so much less weight with upper management.<p>So, where I&#x27;m going with this is -- if you work for a company in an infosec field and you genuinely want to improve things to the point where management actually starts to listen (which translates into $$ for your team and your projects), then you need to both convince them that your expertise is equally as important as the lawyers&#x27;, and probably present yourself with the same amount of gravitas as those working on the legal team.