Cloud, code and AI security
We find the problems and we fix them.
We scan your cloud accounts, your code and the AI agents you run. We write each fix and open it as a pull request for your team to review.
Read-only access. Nothing to install.
One product for cloud security and AI security: attack paths across both, fixes as pull requests in your IaC code, and blocks for risky AI agent actions.
One product and one price. Plans from €0, no per-seat charges, no per-resource metering.
- Cloud security (CSPM)
- AI agent security
- Attack paths across cloud and AI
- Fixes as pull requests
- Blocks for risky agent actions
Cloud security
From the internet to your data, every hop checked.
Your AWS, Azure and Google Cloud accounts, scanned on a schedule and when things change.
- 1. Internetanyone, anywhereEntry
- 2. Security groupsg-web · 0.0.0.0/0 on 22Verified: reachable
- 3. Instanceweb-1Verified
- 4. IAM roleweb-instance-roleVerified against your accountCut here
- 5. Crown jewelacme-customers (S3 bucket)Consequential
Find
Misconfigurations, drift from your IaC code, and the code that created each resource.
Paths
Every hop checked against your account. The choke point that breaks the most paths, named first.
Fix
A pull request in your IaC code, planned against your real state, so the next deploy keeps it.
AI agent security
What your AI agents can reach, and the one call that must not run.
Each Amazon Bedrock agent in your AWS accounts, its tools, the roles they run as, and the data behind them.
- 1. Untrusted documentonboarding-guide.pdf in acme-support-docsNot confirmed: whether untrusted text can steer this agent
- 2. Agentacme-support-assistantVerified: read from your account
- 3. Action group, Lambda toolcloud layercustomer-tools → acme-support-toolsVerified against your account
- 4. IAM rolecloud layeracme-support-tools-role → acme-data-reader (account 2222…)Not confirmed: the role is in another accountCut here
- 5. Crown jewelcloud layeracme-customers (DynamoDB table, account 2222…)No undo
Find
What each agent could read, change or delete, and which of that cannot be undone.
Paths
Untrusted input, agent, tool, role, data: one path across the AI and cloud layers, every hop checked.
Fix and block
A pull request that removes the risky permission, and the runtime gate (Enterprise plan, opt-in) that blocks the destructive call. Netlumi never reads prompts or replies.
Prove it
Prove it on your own agent.
Plant one harmless instruction, run your agent as you normally do, and see what it did.
Plant it
Wherever your agent takes input: a chat message, a document, a knowledge-base entry, an email or ticket, a web page, a tool result.
Run it
Run your agent as you normally do.
See what it did
Netlumi shows the write it made, whether it can be undone, and the fix.
Netlumi never runs your agent and never reads your prompts.
Less noise
Critical and high only when verified.
A short list, not a pile of alerts. An issue is critical or high only when it is exploitable, reachable, verified and consequential.
- One issue per root cause, not one finding per setting.
- “Not confirmed” is a state with a reason, never a downgrade to “fine”.
Every verified critical reaches you at once. Beyond that, at most one urgent alert per account a week; the rest goes into the daily digest. Our automatic remediation workflow keeps fixing them meanwhile.
Trust
Read-only. Nothing to install. Here is what we keep.
Read-only access
An AWS role assumed with an external ID for one-hour credentials, or workload identity federation for Azure and GCP. No stored access keys.
Nothing to install
Netlumi is agentless. Scans use read-only access. Fixes arrive as pull requests you review.
Code access
A read-only GitHub app for scanning. A separate fix app opens pull requests on the repositories you choose.
SOC 2 Type I and ISO 27001: in progress.
Trust and data handlingSecurity pageFrom the founder
I worked in security for 15 years at AWS, CrowdStrike and McAfee. Companies have more security findings than they can fix. Security teams find the issues, but development teams own the infrastructure and the code. The findings go back and forth between them, the pile of alerts grows, and the systems stay exposed the whole time. I started Netlumi to find the cloud, code and AI issues that matter and open a pull request with the fix, so the team only has to review and merge it.
Questions
Questions buyers ask.
What does Netlumi do?
Cloud security (CSPM). AI agent security. Attack paths across cloud and AI. Fixes as pull requests. Blocks for risky agent actions. We scan your AWS, Azure and Google Cloud accounts, your repositories and the AI agents you run, and open the fix as a pull request in your IaC code for your team to review and merge.
Why not just use AWS Security Hub?
Keep Security Hub on; the two work together. Security Hub collects findings about your AWS accounts, and its automated response changes the live resource. Netlumi fixes the IaC code that created the resource, with a pull request you merge, so the fix is still there after the next deploy. Netlumi shows which findings chain into a path to your data and marks critical or high only when the path is exploitable, reachable, verified and consequential, so you get a short list. Netlumi also maps what your Amazon Bedrock agents can reach and change, including actions that cannot be undone, can block risky tool calls before they run (the runtime gate, Enterprise plan), and places decoy credentials that catch misuse. And Netlumi covers Azure and Google Cloud, and your code and repositories.
What permissions does Netlumi need?
Read-only. On AWS you create a role with the AWS-managed SecurityAudit policy plus Netlumi policies that grant exactly the read actions Netlumi calls, and Deny policies that stop it reading your data (S3 objects, DynamoDB items, log events, queue messages, secrets). Netlumi assumes the role with an external ID for credentials that expire after one hour and stores no access keys. Azure uses a federated credential and Google Cloud uses workload identity federation, with no stored secrets. For GitHub, a read-only app scans your repositories, and a separate fix app opens pull requests on the repositories you choose.
What data does Netlumi store, and where?
Findings, inventory and attack paths from your cloud accounts; for connected repositories, a working copy on encrypted disks while the repository is connected, and proposed fixes for up to 30 days. Netlumi's search index does not keep the text of your code. Secrets Netlumi finds are recorded by name and a short fingerprint, never in full. Everything is encrypted in transit and at rest, with a key per tenant. Service logs are kept for 30 days.
More questions
Is my data used to train AI models?
No. Netlumi does not use your data to train AI models. Where Netlumi sends code context or findings to an AI provider to write a fix or answer a Lens question, secrets are masked first, and the providers are listed on the Security & Privacy page in the app.
Does Netlumi change my cloud or merge code?
No. Netlumi has no write access to your cloud. Fixes arrive as a pull request on a netlumi/fix-* branch; Netlumi never pushes to your default branch and never merges. Your team reviews and merges, and your pipeline applies the change as it would any other.
How many cloud accounts does each plan cover? Does the Starter plan cover 20 accounts?
No. Starter ($249 a month) covers up to 3 cloud accounts, Growth up to 10, Enterprise up to 25, and the free Developer plan 1. A cloud account is one AWS account, Azure subscription or GCP project. 20 or more accounts means the Enterprise plan; for more than 25, talk to us. Users are unlimited on every plan.
How does the price compare to buying separate tools?
One product and one price. Plans from €0, no per-seat charges, no per-resource metering. Teams otherwise buy a cloud posture tool, an AI security tool and a fix workflow separately, and pay for each. Netlumi is one subscription: €0 / €229 / €499 / €999 a month for the Developer, Starter, Growth, Enterprise plans, with unlimited users. A team with 20 or more cloud accounts is the Enterprise plan, €999 a month for up to 25 accounts, so nobody has to guess what the Starter price covers.
Does Netlumi cover Amazon Bedrock agents?
Yes. Netlumi lists the Bedrock agents in your AWS accounts, follows each agent through its action groups and the Lambda functions and IAM roles its tools run as, and shows the data each agent could read, change or delete, including data in another account, and which of those actions cannot be undone. It shows the path from untrusted input, such as a document with a prompt injection, to your data, and the change that breaks it. Agent reach and AI attack paths cover AWS today.
Can I test this on my own agent?
Yes: Prove it. Plant one harmless instruction wherever your agent takes input (a chat message, a document, a knowledge-base entry, an email or ticket, a web page, a tool result), run your agent as you normally do, and Netlumi shows the write it made, whether it can be undone, and the fix. Netlumi never runs your agent and never reads your prompts.
Which clouds and AI platforms does Netlumi support?
AWS, Azure and Google Cloud for cloud security. For AI: Amazon Bedrock and SageMaker models, endpoints and agents are checked in your AWS accounts; Azure OpenAI and Google Vertex AI usage is detected in your code. The runtime gate sits in front of the tool calls your agent gateway makes, in your AWS account.
What if I have more than one issue at once?
Every verified critical reaches you at once. Beyond that, at most one urgent alert per account a week; the rest goes into the daily digest. Our automatic remediation workflow keeps fixing them meanwhile. Each fix arrives as a pull request you review.
Does Netlumi have a SOC 2 report or an ISO 27001 certificate?
Not yet. SOC 2 Type I and ISO 27001 are in progress. Netlumi runs an information security management system aligned to ISO/IEC 27001:2022 Annex A, can walk you through it and answers security questionnaires on request. We will publish the reports when they are issued.
What happens when I cancel or leave?
Plans are billed monthly or yearly; a monthly plan has no annual commitment. When a trial ends you pick a plan or drop to the free plan, and nothing is deleted. When you remove the role from a cloud account, its data is kept for 30 days so a reconnect restores it, then purged. If another organisation takes the account over, your copy is purged at once. On request, Netlumi deletes your whole organisation and destroys its tenant key first.
Scan a repo free. No signup.
Or see the live demo, sign up, email us or book a meeting.