What would stop someone from publishing sensitive information to the "public?"

I was just thinking about the upcoming WFR and how historically it's always been the same few departments that get hit hard. Those departments don't exactly hold much - if any - truly sensitive data I think? idk, to me it seems like certain departments rarely ever get hit due to what those employees do and posses?

I am a bit surprised that you don't hear of companies having their internal sht released publicly and/or to dark web type sites very often. I'm sure it happens all the time but I'm not one who keeps up with that stuff so idk.

A network engineer for example could release a massive list of internal network maps. Those who manage firewalls could release the entire rule base of what is in the firewalls. A person in sales could release a list of clients they have, or clients they won't work with possibly, etc... Or maybe someone who works with PCI stuff releases a giant list of customer names/address's/CC info?

In my mind I think anyone who does that is stupid, first of all. But those who do it I suppose do it for a profit? Which still seems d-mb because I feel there is a high chance of getting caught anyways.

#PCI #WFR

Comment! It's anonymous!

15 replies (most recent on top)

@nm In contrast to cases where an individual can be sued for leaking sensitive company information, reporting a GPL violation to the media can have the opposite effect: the violator company may lose the right to legally use, modify, or distribute the software until the situation is remedied. Legal action is another possible outcome. The copyright holder, often the original author or a contributor to the project, may choose to file a lawsuit against the violator.

Prison

Probably getting sued

@j0 I mean obviously... It is a theoretical question lol. Which IMPO is why certain departments rarely ever get hit by layoffs

@cy I don't believe there is any "code" for the NDA lol... I am part of it and even if you did release something, it's not proprietary nor is it likely to be detrimental to Dell.

Okay, I’m going to sound like your kindergarten teacher.
Placing sensitive information out there to the world or selling it to a hacker is a criminal offense. I don’t care how much you feel you were wronged by Dell, that intellectual property is not yours. You agreed to that the day you were hired. More so, for some jobs it may involve national security

Making such info public or selling it makes you as bad or worse than any Dell. Exec.

And there’s a good chance you will be caught.

Don’t get caught…

@cp that's the code i put on github

Release the project maverick!! All these NDA folks are safe and sound!!

I put the applications code that I worked on on github.

@af Assuming they get caught yes lol. What if they were to sell this info to the highest bidder, then move to idk.. china?

Jail time is the answer

@a2 Yeah but at the same time, I feel like if someone has been at Dell for idk say, 15 years maybe and are nearing retirement age, then are let go and blindsided, what do they have to lose? Their "dignity" was ripped away from them and now they likely will never find a new job due to age.

Imagine the kind of havoc a 55 year old senior network engineer or cyber engineer who'd been at Dell for 15+ years - or he-l, even less than that - could cause if they wanted to do so out of spite? They'd know the innerworkings of how things work, what the routing is, what is allowed/blocked - both internally and externally. What dignity would they be trying to save?

Because people have dignity, not Dell though.

I'm in Tech Support but have a friend in Cyber Security - not at Dell - and he was laid off semi recently. He was telling me how he could have sold every type of internal networks, IP's, firewalls, etc... to hackers if he wanted to.

Thread regarding Dell Inc. layoffs

What would stop someone from publishing sensitive information to the "public?"

15 replies (most recent on top)

Post a reply