Securitain Podcast · 22-Minute Product Deep Dive

Powerful AWS Security Analysis.Read-Only by Design.

Securitain helps AWS teams understand IAM risk, privilege escalation paths, blast radius, trust exposure, and compliance gaps — without asking for unnecessary control over customer cloud environments. Temporary STS access, read-only permissions, ExternalId protection, and customer-owned CloudFormation roles.

Securitain is powerful in analysis, but limited in authority.

Best for AWS leaders, cloud architects, security engineers, compliance teams, SaaS founders, and DevSecOps teams.

Listen to the Podcast

Episode length: 22 minutes · How Securitain protects customer trust while analyzing AWS risk

Quick Summary

Security tools should not create new security risks

Securitain inspects AWS environments deeply while keeping access controlled, temporary, and view-only. Customers connect their AWS account through a CloudFormation-deployed audit role. Securitain then uses AWS STS AssumeRole with ExternalId protection to perform read-only security analysis.

No long-lived AWS access keys.
No customer AWS write permissions.
No direct auto-remediation.
No unnecessary control over customer resources.

The result is a security platform that helps teams understand risk without handing over control.

Security Design Principles

Trust earned through architecture

Customer-Controlled Access

Customers deploy the audit role in their own AWS account. The customer owns the role, the CloudFormation stack, and the trust relationship — and can remove access by deleting the stack or disabling the role.

Temporary Credentials

Securitain uses AWS STS AssumeRole to obtain temporary credentials for scanning. The platform does not require long-lived AWS access keys.

Read-Only Inspection

Designed for inspection, not control. It collects AWS security evidence using read-only permissions and does not directly modify customer AWS resources.

ExternalId Protection

Each customer connection uses a unique ExternalId. This helps protect cross-account role assumption and reduces confused-deputy risk.

No Auto-Remediation by Default

Securitain can generate remediation guidance, CLI examples, and Terraform-style recommendations — but it does not automatically change customer AWS accounts in the current design.

Tenant-Aware SaaS Architecture

A multi-tenant SaaS platform where customer data is scoped by organization, and backend APIs resolve tenant identity from authenticated user context.

Transparent Capability Checks

After account connection, Securitain checks what it can analyze. If optional permissions are missing, it shows partial capability status instead of silently producing incomplete results.

What Securitain Analyzes

AWS IAM & identity risk across layers

IAM Inventory

  • •Users
  • •Roles
  • •Groups
  • •Managed & inline policies
  • •Access keys
  • •Permission sets
  • •Trust & resource policies

Credential Hygiene

  • •Missing MFA
  • •Root account risks
  • •Old / inactive access keys
  • •Multiple active keys
  • •Password age risk

Permission Risk

  • •Wildcard actions & resources
  • •AdministratorAccess
  • •IAM mutation permissions
  • •PassRole risk
  • •Sensitive data permissions
  • •Security control disablement

Privilege Escalation

  • •Who can become admin?
  • •Who can pass a powerful role?
  • •Who can modify policies or trust?
  • •Lambda / EC2 / ECS / CFN / CodeBuild / SageMaker / Glue escalation

Toxic Combinations

  • •PassRole + Lambda create/update
  • •PassRole + EC2 RunInstances
  • •KMS Decrypt + S3 GetObject
  • •CloudTrail StopLogging + IAM mutation
  • •GuardDuty/SecurityHub disable + escalation

Cross-Account Exposure

  • •External AWS / root principal trust
  • •Missing ExternalId or PrincipalOrgID
  • •Wildcard principals
  • •External KMS decrypt / S3 / Lambda invoke

Federation & OIDC Risk

  • •GitHub Actions OIDC trust
  • •Missing audience / subject condition
  • •Wildcard repository trust
  • •All branches allowed
  • •Admin roles trusted by external IdP

Blast Radius

  • •Can it become admin?
  • •Access sensitive data / decrypt KMS?
  • •Read secrets?
  • •Assume roles across accounts?
  • •Disable logging?
  • •Impact production?
CIS AWS FoundationsSOC 2NISTHIPAAPCI DSSAWS Well-Architected
How the Connection Works

From onboarding to safe recommendations

1

Create Connection Intent

Customer starts onboarding inside Securitain, which generates a unique connection intent and ExternalId.

2

Deploy CloudFormation

Customer launches the CloudFormation template in their AWS account, creating a dedicated Securitain audit role.

3

Assume Role with STS

When a scan runs, Securitain uses AWS STS AssumeRole with the customer-specific ExternalId.

4

Run Read-Only Scan

Securitain collects IAM, identity, policy, activity, exposure, and compliance evidence using read-only AWS APIs.

5

Analyze and Prioritize

Calculates risk, identifies findings, maps compliance controls, detects escalation paths, and ranks by severity and blast radius.

6

Recommend Safely

Provides remediation guidance while customers remain in control of applying changes.

From Alerts to Understanding

Traditional dashboards stop at

“This IAM policy is risky.”

Securitain helps explain
  • Why is it risky? Who is affected?
  • What can this identity reach?
  • Can this become a privilege escalation path?
  • Is customer data exposed?
  • Which compliance controls are impacted?
  • What should be fixed first — and safest path?
Who This Is For

Deeper visibility without operational risk

Cloud Architects

Understand IAM risk across AWS accounts and identify dangerous trust or permission patterns.

Security Engineers

Find privilege escalation paths, toxic combinations, and identities with high blast radius.

DevSecOps Teams

Review CI/CD roles, GitHub OIDC trust, deployment permissions, and policy drift.

Compliance Teams

Connect technical findings to CIS, SOC 2, NIST, HIPAA, PCI DSS, and AWS Well-Architected.

SaaS & SMB Leaders

Get a practical view of cloud security risk without deploying a heavy enterprise platform.

MSPs & Consultants

Use structured findings, reports, and remediation guidance to support customer security reviews.

Example Questions Securitain Helps Answer

Who can become admin in this AWS account?
Which IAM roles have dangerous external trust?
Which access keys are old, inactive, or attached to privileged users?
Which policies allow wildcard access?
Which identities can read S3 and decrypt KMS data?
Which CI/CD roles can deploy with excessive permissions?
Which GitHub OIDC trust policies are too broad?
Which identities can disable CloudTrail, GuardDuty, or SecurityHub?
Which findings map to CIS, SOC 2, NIST, HIPAA, or PCI DSS?
Which issue should we fix first based on blast radius?
Podcast Episode Guide

What's inside the 22 minutes

▶
00:00

Why Security Products Must Prove Their Own Security

If Securitain scans customer clouds, how is it designed to avoid becoming a risk?

▶
03:00

Why Securitain Avoids Long-Lived AWS Keys

Why temporary STS access is safer than storing static AWS credentials.

▶
06:00

Read-Only by Design

The importance of view-only inspection and why write permissions are not requested.

▶
09:00

ExternalId and Cross-Account Trust

How ExternalId protects the customer-owned audit role from confused-deputy risk.

▶
12:00

Why Auto-Remediation Is Not the Default

Why remediation should be explainable, reviewable, and customer-approved.

▶
15:00

How Securitain Finds Hidden IAM Risk

Privilege escalation, toxic combinations, blast radius, trust exposure, and compliance mapping.

▶
19:00

Final Takeaway

Securitain’s design principle: powerful in analysis, limited in authority.

Trust Statement

Securitain is being designed with the same security mindset it promotes to customers. It does not ask customers to give up unnecessary control, does not require long-lived AWS access keys, does not directly modify customer AWS resources, and does not treat remediation as something that should happen invisibly in the background.

Transparent accessTemporary credentialsRead-only inspectionEvidence-based findingsExplainable riskCustomer-approved remediation

Security is not only what Securitain detects.
Security is how Securitain operates.

FAQ

Security-first architecture, explained

No. Securitain is designed to use AWS STS AssumeRole with temporary credentials instead of long-lived customer AWS access keys.

See AWS Risk Clearly — Without Giving Up Control

Securitain helps AWS teams identify IAM risk, privilege escalation paths, blast radius, cross-account exposure, and compliance gaps using a security-first access model.

Temporary STS accessRead-only inspectionExternalId protectionCustomer-controlled audit roleManual remediation guidanceEvidence-based reporting

Stay in the loop

Cloud security insights, early access & compliance updates

Weekly InsightsEarly AccessExpert Content
No spam, everUnsubscribe anytimeWeekly updates
Chat with Securitain