Discover your cloud security risks before attackers do

Jutsu reads the configuration of your AWS, Google Cloud, and Azure accounts with read-only access, finds the misconfigurations, risks, and compliance gaps, rates each one, and tells you how to fix it. Your first posture report is free.

Jutsu dashboard
Jutsu · SOC overview
  • Read-only, no agentsJutsu reads your configuration through read-only roles. Nothing is installed in your cloud.
  • AWS, Google Cloud, Azure37 checks for AWS, 20 for Google Cloud, and 35 for Azure, plus GitHub, Workspace, and your deploy platforms.
  • A fix for every findingConsole steps and commands that use your resource's real name, and a way to confirm the fix.
  • A report you can shareTop risks, findings by check, and what passed, in a report that exports to PDF.

What is a cloud security posture assessment?

Configuration, not code

A cloud security posture assessment reads how your cloud accounts are set up and compares it with known-good settings: who can sign in and how, what can be reached from the internet, what is encrypted, and what is logged. Each gap it finds is a misconfiguration, a security risk, or a compliance gap, and often all three.

It answers a different question from monitoring. Security monitoring asks what is happening right now; a posture assessment asks what could happen because of how things are set up. A public storage bucket, a root user without multi-factor sign-in, or a database with an address on the internet needs no clever exploit. It only needs to be found.

What Jutsu checks

Each connected account gets the checks for its provider. They run every day, and you can run them on demand; a new connection is picked up the same day.

  • AWS: 37 checks, from public buckets and root-user multi-factor sign-in to CloudTrail in every region, GuardDuty, AWS Config, VPC flow logs, IMDSv2, encrypted disks and databases, public snapshots, and access-key age. Failed Security Hub controls come in as findings too.
  • Google Cloud: 20 checks, including public buckets and projects, firewall rules open to the internet, OS Login and Shielded VM, Cloud SQL public addresses, encryption, and backups, downloadable service-account keys, broad Owner and Editor roles, and data-access audit logs. Security Command Center findings come in as well.
  • Microsoft Azure: 35 CIS-based checks, including Remote Desktop and SSH open to the internet, SQL auditing, firewalls, and TLS, anonymous storage access, Defender for Cloud plans, activity log export and alerts, and HTTPS on web apps. Defender for Cloud recommendations come in as findings.
  • The platforms you build on: GitHub (13 checks, such as branch protection, secret scanning, push protection, Dependabot, and required two-factor authentication), Google Workspace (6, such as 2-Step Verification, super admins, and dormant accounts), Cloudflare (13), Vercel (9), Railway (10), and Supabase (8, including row-level security and point-in-time recovery).

Read-only, with nothing to install

The assessment is agentless. Jutsu reads configuration through roles that can look but not change: an audit role with AWS's SecurityAudit and ViewOnlyAccess managed policies, created from a CloudFormation template, with no access keys; the Viewer and Security Reviewer roles in Google Cloud; and Reader, plus Security Reader for Defender for Cloud, in Azure. GitHub connects through a read-only GitHub App and Google Workspace through read-only scopes.

The categories of findings

The checks fall into a few groups. Each finding is rated low, medium, high, or critical.

  • Internet exposure: public buckets and projects, databases with a public address, and firewall rules that open SSH, Remote Desktop, or every port to the internet.
  • Identity and access: multi-factor sign-in for the root user and console users, root access keys, old or unused access keys, downloadable service-account keys, and broad owner roles.
  • Data protection: encryption of buckets, disks, and databases, encrypted connections, backups, and versions kept of stored files.
  • Logging and detection: CloudTrail in every region, data-access audit logs, the Azure activity log, GuardDuty, and Defender for Cloud, so you would see an attack in progress.
  • Code and delivery: branch protection, required reviews, secret scanning, push protection, and Dependabot on GitHub.

From finding to fix

A list of problems is only useful if it says what to do next. Each finding in Jutsu comes with the next step.

  • Fix steps: the console steps, the exact commands with your resource's real name filled in, a command to confirm the fix, and the permissions you need to make it.
  • Grouped by check: a check that fails on ten buckets is one row on the Risks page, not ten, and you can hand the whole group to one owner.
  • Check again: after a fix, ask Jutsu to run the check again. The risk closes once it passes.
  • Fix with your AI agent: open a finding in Claude Code, Claude Desktop, or Cursor with a prompt that links to it. Nothing is sent until you press Enter, and the Jutsu MCP server gives your agent the fix brief.

The posture report

The cloud account security report covers one AWS, Google Cloud, or Azure account. It opens with an executive summary and the top risks, then lists the findings by check with their fixes, what Security Hub, Security Command Center, or Defender for Cloud raised, the last 30 days of alert activity, the checks that passed, the findings you accepted, and an appendix of failing resources. It exports to PDF, for your team, your board, or a customer's security review.

Your first report is free. When you sign up, Jutsu runs the AWS, Google Cloud, Google Workspace, and GitHub checks once, on any plan, and puts the results in a Posture Report you can save as a PDF. Daily checks and the cloud account security report come with every paid plan.

What to fix first

Severity tells you how bad a finding is; reachability tells you how soon it matters. A sensible order for a small team:

  • Anything open to the internet: public storage, databases with a public address, and SSH or Remote Desktop open to everyone.
  • The keys to the account: multi-factor sign-in on the root user and every console user, and no root access keys.
  • Logging: CloudTrail, audit logs, and the activity log switched on everywhere, so the next problem leaves a trace.
  • Data protection and hardening: encryption, backups, and the medium and low findings, worked through as a backlog.

Posture, compliance, and where this stops

The same daily results feed the evidence tasks in Jutsu's Compliance module, for SOC 2, ISO 27001, and 11 more frameworks. SOC 2 for startups explains how. The report itself lists checks, not framework controls.

A posture assessment reads settings. It doesn't watch live activity (that is what monitoring is for), it doesn't scan your application code, and it isn't a penetration test: nothing tries to break in. It also sees only the accounts you connect.

An example posture report

Real Jutsu checks, the severity each one carries, and the fix it points to. Your report names your own resources.

Check that failedWhereSeverityRecommended fix
No storage bucket is open to the publicAWSCriticalTurn on Block Public Access for the bucket, then check again.
The root user has multi-factor sign-inAWSCriticalAdd a multi-factor device to the root user, and keep the root user out of daily work.
No firewall rule lets the whole internet reach remote sign-in portsAWSCriticalNarrow the security group rule for SSH or Remote Desktop to the addresses that need it.
Databases have no address on the public internetGoogle CloudCriticalRemove the Cloud SQL instance's public address and connect over a private network.
Service accounts have no downloadable keysGoogle CloudHighDelete the downloaded key and let the workload use its attached service account.
Storage accounts do not allow anonymous blob accessAzureHighTurn off anonymous blob access on the storage account.
Changes to the default branch need an approving review that nobody can skipGitHubHighRequire an approving review on the default branch, with no bypass for admins.
Storage buckets keep old versions of their filesAWSLowTurn on versioning, so a deleted or overwritten file can be recovered.

An illustration: the checks and their severities are Jutsu's, and the selection is ours. A real report covers one account and lists every check that ran, failed or passed.

Three steps, end to end

  1. Connect a cloud account

    AWS through a CloudFormation template and no access keys. Google Cloud and Azure take about 10 minutes, with read-only roles.

  2. The checks run

    Every check for that provider runs the same day, then every day after, and whenever you ask.

  3. Fix, then check again

    Work down the findings by severity with the fix steps, and re-run a check to close it.

What the assessment gives you

  • Daily configuration checks

    AWS, Google Cloud, Azure, GitHub, Google Workspace, Cloudflare, Vercel, Railway, and Supabase, every day.

  • A severity on every finding

    Low, medium, high, or critical, with Security Hub, Security Command Center, and Defender findings mapped in.

  • Fix steps with real names

    Console steps and commands for the bucket, user, or project that failed, and a command to confirm.

  • Check again on demand

    Re-run a check after a fix. The risk closes once it passes.

  • Grouped by check

    One failing check across many resources is one row, with one owner.

  • A report in PDF

    Executive summary, top risks, findings by check, and what passed, for one account.

Common questions

What is a cloud security posture assessment?

It is a review of how your cloud accounts are configured, compared with known-good settings: who can sign in and how, what can be reached from the internet, what is encrypted, and what is logged. It finds misconfigurations before someone uses them. Jutsu runs it as read-only checks against AWS, Google Cloud, and Azure, and against GitHub, Google Workspace, Cloudflare, Vercel, Railway, and Supabase.

Which clouds does Jutsu assess?

AWS (37 checks), Google Cloud (20), and Microsoft Azure (35 CIS-based checks). Failed Security Hub controls, Security Command Center findings, and Defender for Cloud recommendations come in as findings too. Jutsu also checks GitHub, Google Workspace, Cloudflare, Vercel, Railway, and Supabase.

Does Jutsu need write access or an agent in our cloud?

No. The assessment is agentless and read-only. AWS uses an audit role, created from a CloudFormation template, with the SecurityAudit and ViewOnlyAccess managed policies and no access keys. Google Cloud uses the Viewer and Security Reviewer roles, and Azure uses Reader, plus Security Reader for Defender for Cloud. None of these roles can change a resource.

How often are the checks run?

Every day on each connection, and whenever you run them yourself. A new connection is picked up the same day, and after a fix you can ask Jutsu to check again.

What is in the posture report?

The cloud account security report covers one AWS, Google Cloud, or Azure account: an executive summary, the top risks, findings by check with their fixes, provider findings from Security Hub, Security Command Center, or Defender for Cloud, the last 30 days of alert activity, the checks that passed, accepted findings, and an appendix of failing resources. It exports to PDF.

Is the posture report free?

Your first one is. When you sign up, Jutsu runs the AWS, Google Cloud, Google Workspace, and GitHub checks once, on any plan, and gives you a Posture Report you can save as a PDF. Daily checks and the cloud account security report come with every paid plan: Free ($0/month), Startup ($149/month), Growth ($499/month), Enterprise (custom quote).

Is this a penetration test?

No. A posture assessment reads your settings and doesn't try to break in. A penetration test is a separate exercise, done by a pentest firm, that tries to exploit weaknesses. The two find different things, and a customer's security review may ask for both.

Does the report map to CIS or SOC 2?

The Azure checks are based on the CIS benchmark, but the report lists checks, not framework controls. On paid plans the same daily results feed the evidence tasks in Jutsu's Compliance module, for SOC 2, ISO 27001, and 11 more frameworks.

See your cloud the way an attacker would

Connect an AWS or Google Cloud account and get your first posture report free, or book a demo.

Subscribe to our newsletter

Get the latest security tips, product updates, and news delivered to your inbox.