3 ms·
Many (most) processes like that started because someone got burned by something, and the people ultimately responsible said "make a process so it doesn't happen
by zdragnar 7y ago
Many (most) processes like that started because someone got burned by something, and the people ultimately responsible said "make a process so it doesn't happen again".
Often times companies go through this with internal processes as they grow, and some grow out of that phase.
Other times (especially at even larger companies) processes are adopted "from the industry". While not necessarily bad, it also requires flexibility from feedback. In parent's case, auditing to ensure sensitive data is encrypted to a minimum standard is reasonable , auditing to ensure any encryption is limited to a very narrow set of algorithms is not.
I worked on a project once that contracted out security audits to HP and those were distressingly not good security audits, just vague automated checkbox-checking of a list put together with zero context.