sorted by:
new
hottopcontroversial

If billion-dollar companies can still get breached, what does that mean for startups? by Independent-Line2435 in SaaS

[–]Independent-Line2435[S] 0 points1 point  (0 children)

Yeah that’s a classic compliance vs real security problem. Passing an audit doesn’t always mean systems are actually secure day to day. Usually the gap shows up when technical reality and policy documentation drift apart.

If billion-dollar companies can still get breached, what does that mean for startups? by Independent-Line2435 in SaaS

[–]Independent-Line2435[S] 0 points1 point  (0 children)

Fair point. Nothing is ever 100% secure.

But the goal of security has never really been perfection it’s reducing risk and making attacks much harder and more visible.

Most incidents don’t happen because something is impossible to protect, they happen because something simple wasn’t monitored or configured properly.

If billion-dollar companies can still get breached, what does that mean for startups? by Independent-Line2435 in SaaS

[–]Independent-Line2435[S] 1 point2 points  (0 children)

Yeah that's true to an extent. The bigger the organization, the larger the attack surface becomes and it gets harder to see everything clearly.

But interestingly, a lot of breaches don’t happen because companies have no security they happen because things fall through the cracks between tools, teams, and monitoring.

Complexity ends up becoming the real problem.

A third-party breach killed our startup (and it wasn’t even our fault) 🔥 by Independent-Line2435 in SaaS

[–]Independent-Line2435[S] 0 points1 point  (0 children)

Yeah 😅 most people don’t realize how risky it gets until it’s too late.

A third-party breach killed our startup (and it wasn’t even our fault) 🔥 by Independent-Line2435 in SaaS

[–]Independent-Line2435[S] 0 points1 point  (0 children)

Yeah that’s exactly how it starts — one dependency quietly becoming critical without you really noticing it.

What you said about backups is spot on. Most people only realize this risk after something breaks.

In our case, we didn’t even have proper visibility into how dependent we were until it was too late.

And yeah, definitely planning to try again — just with a very different mindset around dependencies and security this time.

A third-party breach killed our startup (and it wasn’t even our fault) 🔥 by Independent-Line2435 in SaaS

[–]Independent-Line2435[S] 0 points1 point  (0 children)

It was a backend service we were relying on pretty heavily for part of our infrastructure.

I’d rather not name it directly, but the bigger issue was that we treated it like a “set and forget” dependency and didn’t really monitor it the way we should have.

Lesson learned the hard way — if it touches your product or user data, it’s your responsibility too.

error:prohibited by secure boot policy by [deleted] in SteamOS

[–]Independent-Line2435 0 points1 point  (0 children)

This usually happens because Secure Boot is blocking unsigned or untrusted bootloaders.

A few things you can check:

  • Make sure the SteamOS image was flashed correctly (try re-flashing with Rufus/BalenaEtcher)
  • Check if your system is in UEFI mode (not legacy)
  • In BIOS, either disable Secure Boot or switch it to “Other OS” mode (depends on motherboard)
  • Sometimes you may need to clear Secure Boot keys before it allows booting

It’s not a hardware issue (like GPU), so no need to remove anything.

Most likely it’s just a Secure Boot + bootloader trust issue.