News for hackers. Stuff that matters.
Re:Microsoft employees exposed internal passwords in securit... by ChrisMarshallNY on Wednesday April 10, 2024 @07:51AM (#39989647)
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 I 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.

Having a policy is worthless, if it is too difficult to follow.

Re:Microsoft employees exposed internal passwords in securit... by Kalium on Wednesday April 10, 2024 @09:18AM (#39990381)
Making 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.

Re:Microsoft employees exposed internal passwords in securit... by consp on Wednesday April 10, 2024 @09:30AM (#39990503)
> 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 ...

Re:Microsoft employees exposed internal passwords in securit... by sofixa on Wednesday April 10, 2024 @09:51AM (#39990733)
I seriously doubt marketing people are spinning up AWS instances.
Re:Microsoft employees exposed internal passwords in securit... by Kalium on Wednesday April 10, 2024 @10:00AM (#39990836)
Once 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.

Re:Microsoft employees exposed internal passwords in securit... by Lord-Jobo on Wednesday April 10, 2024 @10:25AM (#39991055)
It'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
Re:Microsoft employees exposed internal passwords in securit... by sofixa on Wednesday April 10, 2024 @12:33PM (#39992641)
Why would they do that instead of using some SaaS that promises to do everything better like Snowflake or Tableau or whatever?
Re:Microsoft employees exposed internal passwords in securit... by reaperducer on Wednesday April 10, 2024 @04:38PM (#39995468)
Because when they want to get work done they're going to use the first Google result, not spend a week scrutinizing SaaS options.
Re:Microsoft employees exposed internal passwords in securit... by mewpmewp2 on Wednesday April 10, 2024 @05:18PM (#39995827)
I don't think spinning up an AWS instance to do that would be the first Google result though.
Re:Microsoft employees exposed internal passwords in securit... by sofixa on Thursday April 11, 2024 @02:17AM (#39998934)
And the first Google result will be the marketing blog of a SaaS talking about the business value brought by that SaaS, not a how to tutorial on spinning up an AWS EC2 and installing stuff inside.
Re:Microsoft employees exposed internal passwords in securit... by madeofpalk on Wednesday April 10, 2024 @10:00AM (#39990839)
marketing 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
Re:Microsoft employees exposed internal passwords in securit... by shermantanktop on Wednesday April 10, 2024 @10:57AM (#39991416)
10 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.

Re:Microsoft employees exposed internal passwords in securit... by abadpoli on Wednesday April 10, 2024 @10:08AM (#39990916)
Hit 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.

Re:Microsoft employees exposed internal passwords in securit... by Kalium on Wednesday April 10, 2024 @10:49AM (#39991321)
As 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.

Re:Microsoft employees exposed internal passwords in securit... by bluedemon on Wednesday April 10, 2024 @05:41PM (#39996021)
A 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?

Re:Microsoft employees exposed internal passwords in securit... by Kalium on Wednesday April 10, 2024 @10:29PM (#39997832)
Yes. 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.

Re:Microsoft employees exposed internal passwords in securit... by wodenokoto on Wednesday April 10, 2024 @06:13PM (#39996259)
Log in to your vpn, then log in to a website to download a token. Then use said token to log on to a virtual desktop. From here you can open a browser and log in to powerBI, which has access to data in the data warehouse.

Yes, such workflows are something to be routed around.

Re:Microsoft employees exposed internal passwords in securit... by Kalium on Wednesday April 10, 2024 @10:42PM (#39997901)
You're absolutely right. The token is clunky.

The rest - a VPN to a virtual desktop - is entirely reasonable.

Re:Microsoft employees exposed internal passwords in securit... by wodenokoto on Thursday April 11, 2024 @01:09AM (#39998589)
For logging in to an online service?
Re:Microsoft employees exposed internal passwords in securit... by Kalium on Thursday April 11, 2024 @10:16AM (#40002391)
For delivering strict network access controls, a clear audit trail at multiple points, and (at a guess) the usage of very temporary credentials to actually log in, yes. Especially if the same infrastructure is used for other, less SaaS-centric data handling tasks or users are in places that like to mandate access to geo-local data (India, China, etc.).

Security measures in operational workflows are only a little bit about what the end user - you - sees. Generally they're really about delivering something less obviously visible to the user but very valuable to the business, investors, and regulators.

Re:Microsoft employees exposed internal passwords in securit... by riddlemethat on Wednesday April 10, 2024 @10:50AM (#39991332)
What are your recommendations for organizations? Is there guidance for startup companies to follow?
Re:Microsoft employees exposed internal passwords in securit... by ziddoap on Wednesday April 10, 2024 @12:03PM (#39992248)
The NIST Cybersecurity Framework for small businesses is a great starting point for developing and nurturing a healthy cybersecurity program in a startup.

https://www.nist.gov/itl/smallbusinesscyber

https://www.nist.gov/itl/smallbusinesscyber/nist-cybersecuri...

Re:Microsoft employees exposed internal passwords in securit... by abadpoli on Wednesday April 10, 2024 @11:21AM (#39991722)
At my company, the big thing that I think would help is if people would stop treating data engineers as if they are a cheap way to get both software engineering + data analytics in one package. They’re not. Data engineers are brilliant at data things like writing complex pipelines and wicked queries, but they just aren’t as good at writing secure code. Meanwhile, software engineers are the opposite.

Data engineering teams need at least part of their team to be designated software or systems engineers that are experts in stuff like how to create a robust cloud environment. This is not only beneficial for security, but also for cost optimization, performance, operations, etc! It drives me crazy when I see a data engineer or marketing team told they have to fend for themselves when trying to figure out how to build a cloud environment.

Re:Microsoft employees exposed internal passwords in securit... by Kalium on Wednesday April 10, 2024 @10:54AM (#39991365)
In theory, there are documents out there a startup can read, understand, and follow to get reasonable outcomes. Theory is a wonderful place, I'm told. I'd like to visit someday.

In practice, the answer is to hire a consultancy. There are fractional CISO services out there. It's very likely that a startup without significant security experience in-house does not have the expertise to make good use of any guidance they can find. Every scenario is too specific, every personality dynamic too unique, and every new technology question too novel for there to be easy pre-fab answers that a non-security-practioner can find, understand, and apply in a correct and consistent manner.

Re:Microsoft employees exposed internal passwords in securit... by markus_zhang on Wednesday April 10, 2024 @01:38PM (#39993515)
You probably don't really have a proper data engineering teams -- they are most likely BI disguised as DE -- don't ask me how I know it.
Re:Microsoft employees exposed internal passwords in securit... by reaperducer on Wednesday April 10, 2024 @04:18PM (#39995287)
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.

In my organization, the problem is the security people, not the marketing people. They're simply not responsive.

Someone on a non-IT team will send a message to someone in IT Security asking a question, checking to see if a procedure is correct, or if it's OK to so something, and the IT person simply won't get back to them in an acceptable timeframe.

I'm not talking about minutes. I'm talking days. I've seen my coworkers' IT Security tickets go unanswered for more than a week.

Yes, securing your big fancy data warehouse is very important. But guess what — hackers don't knock on the front door anymore. They're going through the small cracks that you allow to form when you don't realize that your job is securing the entire organization, not just your silo.

This is why the rest of the company is going around security to get things done. Because if the money doesn't keep flowing, everyone loses their jobs.

Re:Microsoft employees exposed internal passwords in securit... by abadpoli on Wednesday April 10, 2024 @05:08PM (#39995747)
_Every single person_ in the security industry that I know is on the verge of burnout because we’re all running around trying to answer questions from other teams as fast as possible, but there just simply aren’t enough security people to go around, and I don’t think there ever will be. My security team coworkers each have a backlog of 50-100 unread slack DMs from developer teams looking for guidance at any given time, and it’s been that way for years. My team has been attempting to hire nonstop, but the pace of hiring can’t keep up with the demand.

Honestly, 1 week sounds totally reasonable to me. If you’re at the point where you need an answer immediately or it’s going to delay your timelines, then you didn’t plan your timelines very well, or you waited too long to engage your security team. You have to keep in mind that while you might be laser-focused on your app and think it’s the highest priority, your security team is likely dealing with hundreds of apps, each of which all claim to be the highest priority. Triaging has to happen, and it doesn’t always go in your favor. It really sucks for everyone involved, but I don’t see a good fix for it.

The sweet spot is empowering teams to make most security decisions on their own so the capacity of security people can be spent more wisely and development teams don’t have to wait for an answer except for in very rare cases, but the pessimist in me thinks we’re already too far behind on this and technology (and the opportunity for new security dangers to arise) moves too fast for us to ever catch up.

Re:Microsoft employees exposed internal passwords in securit... by ryandrake on Wednesday April 10, 2024 @05:51PM (#39996089)
I think if you are acting in an advisory role, it's ok to have a backlog and take time to respond. If you are an approver/gatekeeper blocking ship of something, then it's not acceptable to just say "file a ticket, we'll get back to you as workload allows". Maybe have two tiers of tickets: Questions and approvals, giving approvals priority. At my company, the approvers are often the busiest people in the company (busy with other, non-approval related things too) and that never works well. You end up with frustrated clients looking to work around approvals.
Re:Microsoft employees exposed internal passwords in securit... by consumer451 on Wednesday April 10, 2024 @05:07PM (#39995734)
I have no idea if this is realistic, but maybe something like pager duty for security folks would be workable?

Basically, there is always an assigned person on call to oversee the use of any "crown jewel" data?

This way the internal users can continue to move fast, but maybe break way fewer things?

Re:Microsoft employees exposed internal passwords in securit... by abadpoli on Wednesday April 10, 2024 @05:16PM (#39995805)
IME many security people are already on call. What you’re describing is one of the roles of Security Operations Centers, unless I’m misunderstanding what you’re suggesting (which I think might be the case!)

You can’t rely on that as a fix though, because it’s inherently reactive, when what you really want is proactive protections. By the time you get paged about a breach, it’s already too late.

Re:Microsoft employees exposed internal passwords in securit... by consumer451 on Wednesday April 10, 2024 @05:25PM (#39995895)
Thanks, I have no experience in big orgs. What I was trying to get across is a process like:

1) Marketing person wants to play with sensitive data

2) Prior to anything happening, security-aware person is notified

3) Same day, security-aware person deploys the data where the marketing person wanted it, with proper safeguards, hands-off access

edit: I believe you addressed what I am getting at in your recent comment here... https://news.ycombinator.com/item?id=39995747

Re:Microsoft employees exposed internal passwords in securit... by abadpoli on Wednesday April 10, 2024 @05:32PM (#39995950)
I see! I think it’s a good idea, and I personally think that would be a good and overall positive role!

However in my experience in a big org, #1 happens frequently enough where it basically would be needed at all times, and would need a security person (or entire team) dedicated solely to that purpose. And sadly in my experience, companies are not willing to spend the money, or able to hire enough security people, to have that level of a dedicated security concierge for every team that needs it.

Re:Microsoft employees exposed internal passwords in securit... by consumer451 on Wednesday April 10, 2024 @05:37PM (#39995986)
Maybe real security people training the most security-aware person on a given marketing/dev team, and giving them some level of authority? If orgs won't/can't hire enough infosec folks, maybe some of the basic knowledge needs to be spread to other roles?

I may be grasping at straws here. It just feels ridiculous that my national security is being risked by these obviously super-dumb moves made by trillion dollar corporations.

Re:Microsoft employees exposed internal passwords in securit... by Kalium on Wednesday April 10, 2024 @10:45PM (#39997920)
You're describing what's popularly known as a "security champion" program. The problem is you're giving a little bit of training and authority to someone who is primarily accountable for marketing/dev/whatever. At best, this sets up a conflict of interest that the person will occasionally navigate successfully. At worst, they now know enough to be even more dangerous.

The problem isn't just knowledge. The problem is getting people to use that knowledge to push back on bad ideas.

Re:Microsoft employees exposed internal passwords in securit... by consumer451 on Wednesday April 10, 2024 @11:31PM (#39998151)
Thanks. I'm filing that phrase away for future reference. Again, I am just stabbing in the dark from the outside here:

From my external POV, it feels like for all its faults, Google/Alphabet took the time to create BeyondCorp, and does not have the same record of infosec errors that Microsoft seems to regularly display in recent times.

Is that correct? If so, in your opinion, what is the difference? They both print money...

Is this just a difference in "corporate culture?"

Disclaimer: I grew up in Kirkland/Redmond, have a bias that is favorable towards MS, and would love to understand what the heck is happening.

Re:Microsoft employees exposed internal passwords in securit... by Kalium on Thursday April 11, 2024 @10:13AM (#40002365)
Google/Alphabet is willing to mandate - and then enforce - sweeping changes. When they shifted to U2F and forced everyone to use it, phishing all but vanished as an ongoing problem. I don't know if Microsoft is capable of that, technologically or culturally.
Re:Microsoft employees exposed internal passwords in securit... by closeparen on Wednesday April 10, 2024 @05:18PM (#39995826)
Centralized data warehouse. Convenient tools for querying, running arbitrary jobs against, and building reports from that warehouse. Table and column level ACLs. Strong norms and policies against copying/transferring out of the warehouse for any reason except transient UI display. Sufficient capabilities within the warehouse that it's not necessary.
Re:Microsoft employees exposed internal passwords in securit... by deelowe on Wednesday April 10, 2024 @10:14AM (#39990969)
> 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.

Re:Microsoft employees exposed internal passwords in securit... by MichaelZuo on Wednesday April 10, 2024 @10:49AM (#39991317)
Why 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?
Re:Microsoft employees exposed internal passwords in securit... by boblob-law on Wednesday April 10, 2024 @10:52AM (#39991350)
Easy, Cheap, and Fast You can only pick 2.
Re:Microsoft employees exposed internal passwords in securit... by ActionHank on Wednesday April 10, 2024 @11:06AM (#39991537)
I 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.

Re:Microsoft employees exposed internal passwords in securit... by rqtwteye on Wednesday April 10, 2024 @11:55AM (#39992140)
"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?

Re:Microsoft employees exposed internal passwords in securit... by theamk on Wednesday April 10, 2024 @03:22PM (#39994726)
I 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.

Re:Microsoft employees exposed internal passwords in securit... by mewpmewp2 on Wednesday April 10, 2024 @05:11PM (#39995767)
If 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?

Re:Microsoft employees exposed internal passwords in securit... by ChrisMarshallNY on Wednesday April 10, 2024 @05:34PM (#39995968)
Since you asked, there may be a few of us that remember this: https://www.ranker.com/list/dominos-30-minutes-or-less-lawsu...
Re:Microsoft employees exposed internal passwords in securit... by AlexandrB on Wednesday April 10, 2024 @11:25AM (#39991784)
This 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.

Re:Microsoft employees exposed internal passwords in securit... by throwfaraway100 on Wednesday April 10, 2024 @12:49PM (#39992844)
Yes, consequences for negligence and maybe licensure are the only way we'll solve this problem. It's easier to write software without giving a fuck, and if it remains profitable and without consequence, it will continue happening. If you can't write internet-connected software without making basic security errors, you shouldn't be writing software, at least not without the guidance of someone senior (actually senior, not two years post-bootcamp). I can't believe this is controversial.

Lmao I love how suggesting that developers make take responsibility for their work is met with such hostility here. Nice job removing my comments, you jokes of "developers".

Re:Microsoft employees exposed internal passwords in securit... by arrakeenrevived on Wednesday April 10, 2024 @11:10AM (#39991582)
> 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.

Re:Microsoft employees exposed internal passwords in securit... by rqtwteye on Wednesday April 10, 2024 @11:52AM (#39992110)
Seems you are actually working with developers. At my company, the security people just say "no" but don't really work with people who have legitimate needs. So often you end up doing stuff on your personal equipment just to get something done. They also block sites like "nature.com" but don't block downloads from shady download sites.
Re:Microsoft employees exposed internal passwords in securit... by ChrisMarshallNY on Wednesday April 10, 2024 @11:34AM (#39991896)
It'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.

Re:Microsoft employees exposed internal passwords in securit... by buttcomputing on Wednesday April 10, 2024 @12:34PM (#39992649)
At 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?
Re:Microsoft employees exposed internal passwords in securit... by mewpmewp2 on Wednesday April 10, 2024 @05:16PM (#39995809)
Is that security or just UX thing?
Re:Microsoft employees exposed internal passwords in securit... by ChrisMarshallNY on Wednesday April 10, 2024 @05:50PM (#39996083)
> just UX thing?

To engineers, especially ones that use CLIs a lot, "UI" is simply "silly chrome for lusers."

However, the other 90% of users think that it is very important.

I have been looking at the signups for a while, and wondering why the SiA signups have been going unused (or the person tries again, with a non-SiA signup).

It was because of a "UX thing."

It's really, really important to take the "UX thing" seriously. It can make or break products. The OXO line of kitchen gadgets got huge, because the designer's wife was disabled, and he designed tools to make her life easier, which also made everyone else's life easier.

Re:Microsoft employees exposed internal passwords in securit... by mewpmewp2 on Wednesday April 10, 2024 @05:54PM (#39996105)
What was the thing they got confused about and what is the fix?

It's just that it only makes sense to me as a security thing if Sign in with Apple is specifically more secure than other methods of sign in.

I usually like 3rd party logins, don't need passwords, but there's potential for them to be multi-edged sword. Depending on the implementation.

Re:Microsoft employees exposed internal passwords in securit... by ChrisMarshallNY on Wednesday April 10, 2024 @06:15PM (#39996272)
SiA is quite secure, but on my end, it could be quite insecure. It's basically an SSO-type thing.

The workflow is a bit different from the standard login ID/password entry. You use a "Sign In With Apple" button that the OS provides, and that has its own on-device (and cloud) credential generation.

I was not optimizing for the button. There's no need for a user ID, if you are using SiA, so I should not have presented that field to users. Also, some credentials are only available at generation time, and have to be maintained by the app (securely, in the keychain).

That behavior can get reflected in the UI, and may be confusing to folks.

SiA is the only SSO solution we use. I won't use anyone else's code for that stuff, and we keep all user data inside the app. We also don't collect very much.

Re:Microsoft employees exposed internal passwords in securit... by buttcomputing on Wednesday April 10, 2024 @12:27PM (#39992569)
The 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?
Re:Microsoft employees exposed internal passwords in securit... by mewpmewp2 on Wednesday April 10, 2024 @05:20PM (#39995840)
Software changes so rapidly it's incomparable to other fields as you mentioned.
Re:Microsoft employees exposed internal passwords in securit... by akdev1l on Wednesday April 10, 2024 @06:18PM (#39996298)
> 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.

Re:Microsoft employees exposed internal passwords in securit... by johnchristopher on Wednesday April 10, 2024 @12:38PM (#39992704)
> 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 ?

Re:Microsoft employees exposed internal passwords in securit... by akdev1l on Wednesday April 10, 2024 @06:16PM (#39996279)
There are local LLMs but my understand is they are not as good.
Re:Microsoft employees exposed internal passwords in securit... by teeray on Wednesday April 10, 2024 @01:53PM (#39993718)
> 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.

Re:Microsoft employees exposed internal passwords in securit... by unethical_ban on Wednesday April 10, 2024 @05:05PM (#39995715)
I 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.

Re:Microsoft employees exposed internal passwords in securit... by fullspectrumdev on Wednesday April 10, 2024 @06:06PM (#39996198)
> 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.

Re:Microsoft employees exposed internal passwords in securit... by unethical_ban on Wednesday April 10, 2024 @08:55PM (#39997345)
Meh. 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.

Re:Microsoft employees exposed internal passwords in securit... by jjav on Thursday April 11, 2024 @09:03PM (#40008456)
> 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.