Skip to content
Refine

Product · Built by HabileLabs, an AWS Advanced Tier Partner

Know what is exposed in your AWS account, and how to close it.

24 checks across IAM, storage, network, compute, logging and AI services, run every day through the same read-only role as your cost data. Every finding is ranked by severity and carries the AWS Console steps that close it.

  • 24 Checks

    Every one listed below

  • Daily Scan

    Plus on demand

  • Fix Guides

    Console steps + AWS doc

  • AI Services Checks

    Bedrock and SageMaker

Refine's Security Findings page: 8 critical, 73 high, 200 medium and 21 low findings, with each finding naming the resource, the region and a fix
302 findings on one account — 8 critical, 73 high, 200 medium, 21 low — as Refine found them, not a tidied example. Every row names the resource and region; 'Fix available' means Refine has a remediation guide for it, with console steps and the AWS doc — the change itself stays yours to make. Filter by severity, category, region or resource type.

The 24 Checks Catalog

Six categories × four severities. This is every check the scanner runs today, read from the product’s own rule list — no samples, no extras.

CriticalHighMediumLow

"Fix Available" — the steps, not a ticket

A finding that tells you something is wrong and stops there is a to-do, not a fix. Where Refine holds a vetted remediation for a check, the finding carries a Fix Available badge and opens the numbered AWS Console steps that close it — for that resource, in that region.

  • Numbered AWS Console steps, in order, with the official AWS documentation linked at the end
  • Scoped to the finding: the resource ID, resource type and region are on the row you are reading
  • Where the scan returns its own remediation, those steps are shown instead of the curated guide
  • Your IAM role stays read-only. Refine never writes to your AWS account — you apply the change, and you can revoke access at any time

Findings we hold no guide for say so plainly rather than showing an empty panel.

Example finding

Block Public Access to S3 Bucket

acme-prod-logs · s3 · us-east-1

High

How to Fix This (AWS Console Steps)

  1. 1.Open AWS Console and navigate to S3 service
  2. 2.Find and click on the bucket name from the list
  3. 3.Click on "Permissions" tab
  4. 4.Scroll to "Block public access (bucket settings)" section

…5 more steps

View Official AWS Documentation

Where the checks run

Cost data comes from your billing export, so it covers every region on your bill. The security checks are scoped as follows, and every finding names its region.

  • Account-wide

    The four IAM checks — root MFA, old access keys, administrator roles and unused users — cover the whole account.

  • The region you connect

    Storage, database, network, compute and logging checks run in the region the account was connected in. Connect the account where your workloads run.

  • Wherever AI runs

    The SageMaker notebook check walks every enabled region; the Bedrock checks run in every region your bill shows Bedrock spend in.

Security Score

A single 0–100 number that tracks posture trend. Same calibration as the Optimization Score next to it.

Inputs:
All active findings, weighted by severity.
Weighting:
Critical 8× · High 4× · Medium 2× · Low 1×.
Trend:
30-day rolling window with daily snapshots so you see whether posture is improving or eroding.
Filter:
Mute checks you have explicitly accepted (e.g. legacy systems); score recomputes without them.

Example

82/ 100

+4 in 30 days. Driven by closing 3 Critical IAM findings and enabling EBS encryption defaults org-wide.

How we compare

Refine vs. The Alternatives

Honest assessment — Wiz and Prisma are deep CNAPP products, and Security Hub can apply fixes we deliberately cannot. Refine is an AWS-native pairing of security and cost with a free tier and flat paid plans. Different jobs, different prices. Pick the one that fits.

Frequently Asked Questions

  • Each one is a widely used AWS best practice — the kind the CIS AWS Foundations Benchmark and AWS Foundational Security Best Practices ask for: root MFA, no public S3 buckets or databases, no SSH open to the internet, encryption on volumes and databases, CloudTrail and GuardDuty on. The catalogue on this page is generated from the scanner's own rule list, so it is exactly what runs.

Find the security risks already in your AWS account

Connected in minutes. Free under $2,000/month of AWS spend. Read-only access.

Refine is built and supported by HabileLabs, an AWS Advanced Tier Services Partner.