3 ms·
I work in Security and we talk about barrier management. A security barrier is be something you implement to avoid a certain hazard to begin traversing your bow
by unixhero 5y ago
I work in Security and we talk about barrier management. A security barrier is be something you implement to avoid a certain hazard to begin traversing your bowtie risk model (google it).
This particular case of doing a technical check by chcking files" timestamp for timestamps set in the future is NOT a security reason. It is a license compliance check, but has nothing to do with security.
Also, if I were a customer of this company which apparently sells me IT Lifecycle tools that should help me with IT cataloging and omventory, I would be livid if the solution stopped working because it had identified "bad date" files somewhere in my IT landscape. I would migrate the hell away from it there are plenty of other vendors.
- thyrsus 5y agoThe customers for this software are companies like Cadence or Synoptics, who then use it to encourage license compliance by their customers. As a Cadence customer, my employer could use strace to observe the license daemon behavior and figure out how to cheat, but we're not at all interested in doing so, both from an ethical position and as a matter of maintaining a long term relationship. We have dedicated VMs to host the license daemons, so the failure scenarios proposed are unlikely: we've experienced - and corrected - time skews, but they didn't come close to affecting the license servers. Maintaining the license servers are an accepted part of the license cost.
- robertlagrant 5y ago> bowtie risk model (google it). I regret googling it.