6 ms·
This seems to be a common theme. Someone inside a company sets up an Azure/AWS instance, to do sandboxing, and doesn't secure it. Many of these giant data bre
by ChrisMarshallNY 3y ago
This seems to be a common theme.
Someone inside a company sets up an Azure/AWS instance, to do sandboxing, and doesn't secure it.
Many of these giant data breaches, are because some Marketing person, set up an AWS instance, dumped their entire user DB into it, and did a bunch of data mining.
I think that most cloud providers are now defaulting to locked-down, but the issue seems to be, that folks are still going outside their org, to do this.
I suspect that having some kind of secure internal cloud setup would be helpful.
However, and this is a biggie: It needs to be easy to use. So many times, security has so many roadblocks, that folks work around it, simply to be productive.
In my opinion, security needs to be the easiest path. If it is not, then that is the fault of the Security folks; not the end user. I worked for a company that had such terrible security policy, that it basically completely stopped all productivity. You could tell who was violating policy, because they accomplished their goals.
Having a policy is worthless, if it is too difficult to follow.
- Kalium 3y agoMaking doing things right has to be easy. You also need excellent monitoring, because it's inevitable someone will do something else no matter how easy. There are plenty of people and teams who just want a button to push to run their build. That's not so hard. Give them a CI/CD system and they'll use it. The problem becomes the people who want to use weird, wildly divergent build processes made of fifteen shell scripts strung together and downloading arbitrary content from random remote servers because they enjoyed engineering it. They'll insist on having a blank slate of a cloud tenancy because no build system can meet their needs. The CI/CD team does not take this case seriously and will never meaningfully support it. Security is in no way staffed to build out a major extension of the CI/CD service. Perhaps it's the data team, who has decided they would like to datamine large quantities of private information at their leisure, in contravention of privacy policies and contractual language. So they'll jump through hoops and contortions and share passwords every which way in order to do the thing they want. They will deliberately set out to disable monitoring systems because they resent the implications. At no point will they pause to consider if any of this is a good idea. It's not just about making it easy to be secure. It's also about being able to find and stop people being insecure. One of the important things a security policy - and security organization - does is set boundaries for what activity is and isn't permitted. Crossing those boundaries needs to be watched closely... and yes, punished.
- consp 3y ago> are because some Marketing person, set up an AWS instance, dumped their entire user DB into it, and did a bunch of data mining What the actual **. That's a very hefty GDPR violation and you should be fired for doing that. > simply to be productive If you are using private and sensitive data, that should be pretty much out of the question. You develop with a dummy database only, which doesn't matter if leaked. And after having finished testing, move to the actual data. But those damned deadlines ...
- buttcomputing 3y ago[flagged]
- sofixa 3y agoI seriously doubt marketing people are spinning up AWS instances.
- madeofpalk 3y agomarketing orgs often have at least engineering-adjacent people in them. And often they're just disconnected enough from the rest of the engineering org to make mistakes like this
- shermantanktop 3y ago10 years ago, the best tech skills on the marketing team were held by the person who knew Excel really well, including VBA calls to remote data sources. Maybe they were coding from copy/paste examples, but they were coding. Today, give that person an AWS account and they can absolutely build cloud-based data solutions by clicking around and following SO posts. Add ChatGPT to guide them and the sky is the limit…on how much data they can expose.
- Kalium 3y agoOnce they're convinced it's the fastest and easiest way to have a wordpress instance they can publish to as they please, they most certainly are. Or, as in the example, they get the idea that having a database they can analyze will unlock key insights that will drive market share. It doesn't matter if any of this is true. What matters is they believe it and it leaves them feeling empowered enough to invest.
- Lord-Jobo 3y agoIt's not that difficult to do, it's literally day one of a "learning SQL and databases" course. You don't need that much tech savvy to follow a tutorial and start queries in what is a basically a big fancy excel workbook
- sofixa 3y agoWhy would they do that instead of using some SaaS that promises to do everything better like Snowflake or Tableau or whatever?
- abadpoli 3y agoHit the nail on the head. As a security person, the marketing and data engineering teams at my company are what keeps me up at night. They inherently desire to work with the company’s Crown Jewels of data. They want unfettered access to, and want to give other people access to, an entire data warehouse of some of our company’s most sensitive customer information. And when it comes to securing it properly, they often do not have the same engineering capabilities as software teams.
- Kalium 3y agoAs a security person trying to work with marketing and data engineering teams, I've often found them very resistant to learning how to secure things. They generally want to use the tools they know, in the way they know, to do the tasks they understand, on a timeline they find convenient. Anything that tries to get them to understand the risks they are taking or the sensitivity of the data, much less de-risk their workflows, is treated as an obstacle to be routed around. Often, the best I can hope for is a token effort at negotiation where their goal will be to avoid any and all changes on their part. After which I will have to monitor them carefully, because from experience the odds of them backsliding within a week are uncomfortably high. Nothing about this is conducive to producing a healthy environment. When people's idea of "easy" is they can download the company's most sensitive data to their laptop to load into Jupyter, any amount of security controls will come as an imposition.
- bluedemon 3y agoA question for you and anyone else in security: Given that many data engineers have a data science, data analytics, BI, or software engineering background, I'm curious if you've noticed any trends in their approach to data security?
- Kalium 3y agoYes. Generally it can be summarized as "What data security?". Snark aside, there's usually a reflexive assumption that more data is always better and that anything that gets in the way of more data is bad. Anything that limits how data is analyzed is bad. Anything that limits or restricts their choice of tooling or where they use it is rejected. Data scientists and engineers are people who are, often, working with a company's crown jewels. They are trusted with data representing the private lives of hundreds of millions of people assembled in a data warehouse. I want them to have a care. To treat this with due gravitas. All too often, all they seem to see is a neat data set to feed into R on their Macbook.
- deelowe 3y ago> So many times, security has so many roadblocks, that folks work around it, simply to be productive. This has been my experience. We had someone set a secure instance following all the policies and such. Then they moved to another org in the company and I started getting email violations going to the VP every few weeks because they didn't do some sort of attestation. The problem was only the user could do it and the automation had no guidance on how resolve the issue or stop the alerts. This went on for months before it was resolved.
- MichaelZuo 3y agoWhy didn’t the VP escalate it to the CTO/CEO (or whoever could start firing folks and their managers if it wasn’t fixed asap) after the first few emails?
- boblob-law 3y agoEasy, Cheap, and Fast You can only pick 2.
- ActionHank 3y agoI also believe that there is a culture of not actually firing people who do stupid things like this. A mistake is one thing, but negligence is another. Beyond that, whoever allows customer data to be freely accessed and used in cases like this should also be fired. Start culling those who are doing the job poorly to start making space for others who may be able to do it properly.
- AlexandrB 3y agoThis flows from the top down. The consequences to companies that leak private data are so minor why would someone lose their job for risking a leak? At worst it's a fine that amounts to a slap on the wrist. Things that limit civil liability like mandatory arbitration clauses have made this worse.
- rqtwteye 3y ago"Start culling those who are doing the job poorly to start making space for others who may be able to do it properly" How about starting to cull top level managers who constantly put pressure on people, don't hire competent security people but reward quick results that create future problems?
- buttcomputing 3y ago[flagged]
- theamk 3y agoI dunno, if a commercial driver violates speed limits and hits someone, do we want to accept excuses that "It is top level managers' fault for giving me unreasonable timelines which require me to speed?" Sure, the top managers is at fault, but individuals are also responsible for their actions.
- mewpmewp2 3y agoIf that commercial driver was slowly, but methodologically overworked, manipulated, fatigued and pressured into doing this with every incentive promoting speeding, then yes. Why did the driver feel compelled to speed in the first place? Why would there be an environment or incentives where this could be a valid strategy?
- arrakeenrevived 3y ago> security needs to be the easiest path. If it is not, then that is the fault of the Security folks; not the end user. There's truth to what you say, but you're blaming the wrong crowd. Security people are rarely (if ever) the same people that are creating the tools and the security features of the tools you're using. In most cases, I'm powerless as a security engineer to "make security easy to use", the only thing I could do in that regard would be to loosen our security requirements and make our systems less secure, which isn't what you want either. IMO the problem is more that when developing products, security (and ease of security) is still not seen as that important of a feature (if its even seen as a feature at all and not an annoying cost that the product managers have to deal with). In our application security group, we actually do have requirements that any new product being built must have certain security features that make it easier to secure things, but those requirements are often some of the very first things that the product development teams try to justify delaying or ignoring.
- ChrisMarshallNY 3y agoIt's quite possible to develop products that afford security. I'm pretty sure that I know why it doesn't happen, but I won't get into it. In the app I just released, we take security very seriously. I have spent days on just the login screen, tuning it, so that it lubricates the sign on experience. In fact, that's what I'm doing, right now. Some of our users have been getting confused with Sign In With Apple, so I'm looking at ways to make it even smoother.
- buttcomputing 3y agoAt some point, "not taking security seriously" is simply negligence. Other fields already have ways of punishing people for negligence (up to and including suspension of licensure and/or prosecution). Why are software developers immune to consequences for not realizing they need to use parameter binding in their SQL statements?
- mewpmewp2 3y agoIs that security or just UX thing?
- buttcomputing 3y agoThe easiest path is always dangerous, because it's easier to avoid doing the right thing. It's easier to make cars without seatbelts. It's easier to avoid doing quality control for medication. It's easier to put lead in the paint. Somehow, computing hasn't realized that it is a field that maybe actually requires a little specialized knowledge. Would you let any rando fly an airplane? No, of course not. Why are we letting unqualified people write software?
- mewpmewp2 3y agoSoftware changes so rapidly it's incomparable to other fields as you mentioned.
- akdev1l 3y ago> No, of course not. Why are we letting unqualified people write software? Because in 99% of cases the code will never be able to cause harm to a human being and there is zero risk for loss of life. The comparison you are making is kind of ridiculous. To work on the software that works on an airplane then you’ll be vetted appropriately but to work on random CRUD app you don’t really all that much.
- johnchristopher 3y ago> I suspect that having some kind of secure internal cloud setup would be helpful. It has to be secure and functional otherwise people will use office365 or google docs or dropbox. And now I wonder about AI tools. There are no self hosted solutions yet so what will the leaks look like ?
- akdev1l 3y agoThere are local LLMs but my understand is they are not as good.
- teeray 3y ago> security needs to be the easiest path Depends on your definition of “easiest.” It will become the easiest path to conduct business activities by throwing roadblocks into the insecure path. It will not be the “easiest” to use. It’s the equivalent of lowering all the speed limits on every road to 10mph “out of an abundance of caution” instead of doing the hard work of determining the appropriate limits.
- unethical_ban 3y agoI work at a place that uses cyberArk for privileged AD accounts. I have to copy the password from the web UI to login to the system I use every day. If it times out, I have to refresh, respond to 2FA and copy it again. I see coworkers storing their entire password (1 week expiration) in notepad in the meantime. I was going to store the password in a portable Keepass, but I got blocked from accessing a software download website and was scorned by the proxy block page. Frankly, I think the cyberArk method is effing foolish and having regular 2fa integrated into a product's login makes a lot more sense.
- fullspectrumdev 3y ago> I see coworkers storing their entire password (1 week expiration) in notepad in the meantime. There’s nothing inherently wrong with this tbh, from a practical (not policy) security standpoint. If I have code execution on your box and can access your notepad, I can also simply monitor the clipboard for when you copy the creds from cyberark.
- unethical_ban 3y agoMeh. It's a bad habit. And half the time (generally,, not here) people store docs in shared drives. Secure, accessible password storage shouldn't be a burden.
- jjav 3y ago> In my opinion, security needs to be the easiest path. Secure data handling can't ever be the easiest path. The easiest path is to have all data available all the time to everyone with zero access controls. Adding any kind of security to that is going to reduce the ease, even by a tiny amount. Security needs to be pragmatic, people have a job to do and a business to run. Security teams should never forget they are there to enable the business. But at the same time, the company needs to have a culture that recognizes data security is important. If that is not present, there's nothing the security team can do.