• 0 Posts
  • 8 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle

  • This is basically every major enterprise ticketing system. They’re typically extremely customizable over-featured behemoths so that they can check all the buzzword boxes for the people that make purchasing decisions but will never actually use the system.

    "It’s a fully integrated Agile ITIL DevOps CMDB that empowers your users while providing generative KPIs to guide business decisions!”

    Then, on top of that, ownership of it is generally dropped on a team that is completely incapable of properly managing it from both a technical ability and sheer manpower availability standpoint. So each install ends up becoming an overly complex, confusing, terribly performing mess.

    I think I’ve seen one reasonably well managed install in the couple decades I’ve been doing this, a couple of more that were mildly jank but usable, and then everything else has been a pit of despair largely driven by the above.


  • commandar@lemmy.worldtoA Boring Dystopia@lemmy.worldSigh.
    link
    fedilink
    arrow-up
    6
    ·
    edit-2
    4 months ago

    Their business model is buying overstock items from other retailers and then reselling it highly discounted. It’s the reason you’ll find things that are Walmart, Target, etc store brands there.

    Basically, it’s anything that aged out in inventory elsewhere that the original retailer no longer wanted taking up shelf space for whatever reason.






  • Cite NIST SP 800-63B.

    Verifiers SHOULD NOT impose other composition rules (e.g., requiring mixtures of different character types or prohibiting consecutively repeated characters) for memorized secrets. Verifiers SHOULD NOT require memorized secrets to be changed arbitrarily (e.g., periodically). However, verifiers SHALL force a change if there is evidence of compromise of the authenticator.

    https://pages.nist.gov/800-63-3/sp800-63b.html

    I’ve successfully used it to tell auditors to fuck off about password rotation in the healthcare space.

    Now, to be in compliance with NIST guidelines, you do also need to require MFA. This document is what federal guidelines are based on, which is why you’re starting to see Federal gov websites require MFA for access.

    Either way, I’d highly encourage everyone to give the full document a read through. Not enough people are aware of it and this revision was shockingly reasonable when it came out a year or two ago.