When Employees Use Software That IT Hasn’t Approved

Re:When Employees Use Software That IT Hasn’t Approved by TeMPOraL on Wednesday June 12, 2019 @06:35PM (#20170050)

> Yes, there are confidential data, but it shouldn't be any real customer data. Right?!?

But it might be. Whenever you're doing software other than for purely internal use, you have a customer that gives you sensitive data which devs absolutely need access to - like requirements for the software you're building!

[ Parent | on HN ]

Re:When Employees Use Software That IT Hasn’t Approved by nitwit005 on Wednesday June 12, 2019 @11:36PM (#20171610)

If you're handing customer data to the developers, it's basically already leaked. Most companies limit who can examine things and get customer sign off first.

[ Parent | on HN ]

Re:When Employees Use Software That IT Hasn’t Approved by TeMPOraL on Thursday June 13, 2019 @03:21AM (#20172489)

Let me reiterate: unless you're doing purely internal tooling, everything about how the software you're making should look and work is essentially sensitive customer data.

[ Parent | on HN ]

Re:When Employees Use Software That IT Hasn’t Approved by nitwit005 on Thursday June 13, 2019 @11:05AM (#20175568)

Actual customer data leaking is generally a legal problem. Your source code leaking is not.

[ Parent | on HN ]

Re:When Employees Use Software That IT Hasn’t Approved by protomyth on Wednesday June 12, 2019 @07:25PM (#20170382)

Keep that on the biz, locked-down side of the network.

[ Parent | on HN ]

Re:When Employees Use Software That IT Hasn’t Approved by TeMPOraL on Thursday June 13, 2019 @03:22AM (#20172495)

I.e. keep JIRA in one network, keep your IDE in the other?

[ Parent | on HN ]