Re:Why we use HTTPS for every .gov website we make
by acdha on Friday November 14, 2014 @02:46PM
(#8609102)
One of the big things you have to remember is that the government is not only large and inconsistent (imagine a F500 with a ton of acquisitions and you're on the right track). I'd put pretty good odds that there's someone who cares at most of those .gov sites and they've been trying to get their management to authorize a fix for many years.
In many cases, they've been prevented from hiring technical staff for a decade or longer so it's not uncommon to find projects which are entirely on life-support, subject to a contract which would require expensive (in both time and money) amendments, etc. The person responsible likely knows about the problem but have zero ability to either fix it directly or get someone else to do.
The other thing you tend to find are poorly considered policies with serious unintended consequences – i.e. for alleged performance/security reasons all traffic is required to go through an agency-wide load-balancer but they didn't buy the SSL module / it's already at capacity and nobody is willing to authorize an exception. (Bonus points if the old single-point-of-failure is scheduled to be replaced by a shiny new SPOF and no changes are allowed until that overdue project ships)
In many cases, they've been prevented from hiring technical staff for a decade or longer so it's not uncommon to find projects which are entirely on life-support, subject to a contract which would require expensive (in both time and money) amendments, etc. The person responsible likely knows about the problem but have zero ability to either fix it directly or get someone else to do.
The other thing you tend to find are poorly considered policies with serious unintended consequences – i.e. for alleged performance/security reasons all traffic is required to go through an agency-wide load-balancer but they didn't buy the SSL module / it's already at capacity and nobody is willing to authorize an exception. (Bonus points if the old single-point-of-failure is scheduled to be replaced by a shiny new SPOF and no changes are allowed until that overdue project ships)