549
NIST proposes barring some of the most nonsensical password rules
(arstechnica.com)
This is a most excellent place for technology news and articles.
It is a boring document but it not impossible to read through, nor understand. The is what compliances officer do. I have a (useless) cybersecurity degree and reading NIST publications is part of my lecture.
My career as a sysadmin consistently has me veering toward security and compliance and my brain is absolutely fried on trying to figure out what these huge docs actually mean, how they apply to the things I'm responsible for and what we're supposed to do about it.
Props to all the folks that can do it without losing their mind.
You need to first understand the grand structure of the doc, then cherry pick the content to action points. At least that's how I do it.
You break it down into chunks and delegate. They're not expecting any one person to implement the whole thing.
Hahaha, tell that to leadership! 😩
Useless??? Ever since the pandemic and the need for a robust remote work infrastructure, the amount of cybersecurity related job offers has exploded. And they're very well paid where I live.
The knowledge and skill are useful, but I can't say the same for the degree
My argument is that if this document (and others) are requirements for companies shouldn't there also be a more approachable document for people to use?
Sure, have the jargon filled document that those in the know can access, but without an additional not so jargon-y document you've just added a barrier to change. Maybe just an abstract of the rule changes on the front page without the jargon?
I don't know, maybe it's not a big deal to compliance officers but just seems to me (someone that isn't a compliance officer) that obfuscating the required changes behind jargon and acronyms is going to slow adoption of the changes.
It needs to be specific to be clear for its purposes. You can express everything in simpler terms but then you risk leaving things out of definitions. It's basically legal speak.
Normally, you'd read the scope of such a document to see whether it fits your purpose, then cherry-pick the chapters necessary. If something's unclear, you can google pretty much everything.
Doing that a few times will make it infinitely easier! You especially get to understand those broad, inaccessible definitions a lot easier.