Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

Plaintext with Rich

Plaintext with Rich artwork

Cloud Security: Why Identity and Configuration Are the Real Perimeter

Jan 16, 20268 minAudio
ShareXLinkedInFacebookWhatsAppEmail

Nothing broke. Nothing crashed. No alarms went off. Someone clicked a box, someone skipped a setting, someone assumed the default was safe. And the cloud did exactly what it was told. This episode explains cloud security by starting with the most important shift: in the cloud, identity is the perimeter. There is no fence, no lobby, no locked server room. If someone has valid credentials, they don't break in, they sign in. The episode walks through how cloud security goes wrong through misconfigured storage, over-permissioned identities, leaked API keys, missing multi-factor authentication, shadow cloud adoption, and absent monitoring. It covers what attackers actually do once inside, from data theft to cryptomining to quiet entrenchment, then closes with a starter kit covering MFA enforcement, least privilege, secret hygiene, storage lockdown, logging, workload hardening, API protection, and guardrail automation. Whether you're moving to the cloud, already there and not sure what to watch, or a leader trying to understand why your team keeps talking about misconfigurations, Plaintext with Rich breaks it down. Is there a topic/term you want me to discuss next? Text me!! YouTube more your speed? → https://links.sith2.com/YouTube Apple Podcasts your usual stop? → https://links.sith2.com/Apple Neither of those? Spotify’s over here → https://links.sith2.com/Spotify Prefer reading quietly at your own pace? → https://links.sith2.com/Blog Join us in The Cyber Sanctuary (no robes required) → https://links.sith2.com/Discord Follow the human behind the microphone → https://links.sith2.com/linkedin Need another way to reach me? That’s here → https://linktr.ee/rich.greene

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Transcript

From the show. Tap a time to play from there.

SPEAKER_00Nothing broke, nothing crashed, no alarms went off. Someone clicked a box, someone skipped a setting, someone assumed the default was safe, and the cloud did exactly what it was told. Welcome to plain text with Rich. Today we're talking about cloud security. Let's really start by grounding the term. In plain text, the cloud is not magic.

SPEAKER_00It's simply computers you don't necessarily own, running in buildings you don't really visit, managed by someone else and rented by the minute. Servers, storage, databases, applications, identity systems. Cloud security is simply the practice of making sure those rented computers only do what you intend them to do and nothing more. And here's the part that changes everything. In the cloud, identity is the perimeter.

SPEAKER_00There is no fence, no lobby, no locked server room. If someone has valid credentials, they don't break in, they simply sign in. Which means cloud security succeeds or fails long before an attacker ever really shows up. It succeeds or fails at configuration time. So how does cloud security usually go wrong? Now, not through clever exploits or cinematic attacks, though they do happen sometimes. It goes wrong through ordinary decisions made under pressure.

SPEAKER_00The most common failure is misconfigured storage. Buckets, drives, or databases get set to public often accidentally. No theft is required. The data is simply reachable. The internet doesn't need to guess, it just shows. Another frequent problem is over permissioned identities. People and applications are given broad access just to keep things moving. Admin rights become convenience tools instead of emergency tools.

SPEAKER_00Now that shortcut feels harmless right up until it isn't. Secrets, leak, right, is another repeat offender. API keys committed to code repositories, credentials pasted in the chat tools, tokens stored in documents or logs. In the cloud, keys are access. Lose the key, lose the boundary. Then there's the absence of multi-factor authentication on powerful accounts. One compromised email, one reused password.

SPEAKER_00Suddenly, an entire environment is exposed. Not because defenses failed, but because they were never turned on. Shadow Cloud adds another layer. Teams adopt SaaS or software as a service tools or spin up cloud resources outside of visibility. The organization's footprint expands, but the oversight never did. Security gaps appear not from verbellion, but from speed. And finally, hey, simply there's monitoring, or more accurately, the lack of it.

SPEAKER_00Many cloud environments are compromised quietly. The first signal isn't an alert. It's a building anomaly or missing data or an uncomfortable external phone call. So, what do attackers actually do once they are in? Usually one of three things. They take data, you know, customer records, internal documents, source code, or backups. They'll abuse compute power. Crypto mining is popular because it's automated and profitable. You pay the bill, they keep the coins. Or they will entrench themselves.

SPEAKER_00New users are created, access keys are added, logs are altered, persistence is established. Again, convenience cuts both ways. The same features that make cloud fast for teams also make it pretty efficient for attackers. So let's shift from failure to prevention. This is going to be our, we'll call it our plain text cloud security starter kit. If we do nothing else, we'll start with these five. First, protect identity with multi-factor authentication, especially for your cloud administrators, your email, your single sign-on accounts.

SPEAKER_00No multi-factor authentication on powerful identities is not a trade-off, it's a gap. Second, enforce lease privilege by default. People and applications should only have the access they need for only as long as they need it. Administrative access should be deliberate, temporary, and visible. Walking around with full access all the time, again, isn't efficiency, it's potential exposure. Third, reduce long-lived secrets, prefer short-lived tokens and managed identities.

SPEAKER_00Rotate credentials, scan code repositories for exposed keys. Because once a secret leaves your control, you simply have to assume it's compromised. Fourth, we want to lock down that storage. Private by default, public only when required, audited regularly. Exposure should be intentional, not accidental. And fifth, turn on logging and alerts. You need visibility into sign-ins, permission changes, key creation, and data access. And you need alerts for the things that matter.

SPEAKER_00New admin accounts, MFA disabled, unusual locations, unexpected downloads. If you can't see it, you can't respond to it. Beyond those, harden what runs inside the cloud. We want to keep workloads updated, remove unused services, limit inbound access, avoid opening things to the world unless there is a clear reason. APIs are going to deserve special attention. They are, in theory, just doors. They should have or need authentication, rate limiting, and some type of validation.

SPEAKER_00Convenience should never be confused with safety. Finally, build some guardrails. Use cloud posture tools and policies to prevent unsafe deployments before they happen. Good cloud security doesn't rely on perfect behavior. It assumes mistakes and contains them. Which brings us to our reality check. The cloud is not less secure than traditional environments. In many ways, it can be more secure, but it is dramatically easier to misconfigure at scale.

SPEAKER_00Small mistakes spread fast, defaults matter, speed amplifies impact. Cloud incidents often aren't hacks, they are missets. So the winning mindset is simple. Assume humans will move fast, assume pressure will exist, design systems that prevent those moments from becoming incidents. That's cloud security. Cloud security is mostly about identity and configuration. If you focus on MFA, least privilege, secret hygiene, private storage and visibility, you prevent the majority of cloud disasters.

SPEAKER_00Again, not with fear, not with heroics, but with intention. And now, if there's a security topic you want broken down in plain text, again, please send it my way. Email me, DM me, drop it in the comments, however you choose to, right? However you reach me, I will read it and I will respond. If this episode helped, share it with someone who'd actually benefit. This has been Plain Text with Rich. 10 minutes or less, one topic, no panic. I'll see you next time.

Open the transcript file

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. After the Click: How to Report a Security Mistake

    Oct 30, 20269 minAudio

    A security mistake can leave you writing and deleting the same message to your manager. You suspect something went wrong, but finding the words feels harder than it should. Plaintext with Rich explores the first useful...

    Credit the people on this episode

  2. Task Scams: Why You Shouldn't Pay to Get Paid

    Oct 23, 20269 minAudio

    Task scams can make an evening of online assignments feel like money earned. Then the withdrawal request turns into another demand, and the balance you've been watching starts to mean something different. Rich traces...

    Credit the people on this episode

  3. Device-Code Phishing: The Real Login Page Trap

    Oct 16, 20269 minAudio

    Device-code phishing starts with an uncomfortable possibility: the sign-in address you checked really does belong to Microsoft. The document you're expecting comes with a code, the page looks right, and the question...

    Credit the people on this episode

  4. Browser Extensions: What Did You Give Permission To?

    Oct 9, 20268 minAudio

    Browser extensions can stay in your working day long after you've forgotten why you installed them. That tiny toolbar icon may represent a bigger arrangement than you remember making. Rich explores what extension...

    Credit the people on this episode

  5. ClickFix: When a CAPTCHA Asks You to Run a Command

    Oct 2, 20269 minAudio

    You came for a conference agenda, and the website wants proof you're human. ClickFix can hide behind that familiar check, with instructions that deserve a much closer look. Rich follows the moment a fake CAPTCHA, a test...

    Credit the people on this episode