Here is the text of the NIST sp800-63b Digital Identity Guidelines.

  • GoofSchmoofer@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 month ago

    It sets both the technical requirements and recommended best practices for determining the validity of methods used to authenticate digital identities online. Organizations that interact with the federal government online are required to be in compliance

    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.

    • 0xD@infosec.pub
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 month ago

      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.