You are reading a single comment by @Velocio and its replies. Click here to read the full conversation.
  • Away from the specs, what's your legal position as an employee using a personal machine? What's the risk of you being held responsible for something going wrong as it is your setup?

    Obviously you're very IT savvy but there does seem to be a higher risk of the device being compromised if it's used as a do everything device. Explaining to a client that their data was exposed due to a bug in Steam or something could be awkward.

  • I don't have customer or employee data on my machine. Compliance requirements (even FedRAMP) don't yet understand "data inside a web browser" as it's all still aligned to "files on disc" which I do not have.

    The code is all OSS, and that which isn't... well we're globally remote and have a BYOD policy that continues to adopt non-corp machines and devices. The key part remains, nothing about a customer leaves the prod environment. No secrets or keys are in any repo either... so even though most of our Cloud stuff is OSS, nothing there can be compromised as the keys aren't held by engineers.

    Basically we treat people like responsible adults, the systems were designed with that in mind, and so this stuff is fine.

    If any of this ever does apply... I'll continue to use the Windows machine for the day-to-day stuff and I have a bling MBP to fall back to for anything "sensitive".

About

Avatar for Velocio @Velocio started