Lacework FortiCNAPP
snapshot-20261104 commercialThe section your link pointed to isn't on Lacework FortiCNAPP's page any more, so we've brought you to the top.
Lacework FortiCNAPP is a cloud-native application protection platform providing visibility, compliance, and threat detection across cloud environments.
curl -X POST 'https://<your-instance>.lacework.net/api/v2/AiAssistants' \
-H 'Authorization: Bearer <token>' \
-H 'Content-Type: application/json' \
-d '{"context": {"alertId": "<alert-id>"}}'
curl -X POST 'https://<instance>.lacework.net/api/v2/AiAssistants' \
-H 'Authorization: Bearer <token>' \
-H 'Content-Type: application/json' \
-d '{"type": "AlertContext", "alertId": "<alert_id>"}'
Summary
Lacework FortiCNAPP is a commercial cloud security platform, run as a SaaSSaaSSoftware delivered over the internet and run on the provider's infrastructure, so the buyer pays a subscription instead of installing or operating anything locally. service, that watches cloud accounts, containers, and code for vulnerabilities, misconfigurations, and runtime threats. It sits within Fortinet's product family alongside tools like FortiDevSec and FortiWeb, aimed at cloud security and DevSecOps teams rather than at network administrators, covering everything from CI/CD pipeline scans to Kubernetes runtime monitoring and AWS, Azure, and GCP log analysis. Its Explorer and Alert Dashboard give practitioners a way to investigate and triage incidents, increasingly with AI-generated incident reports and natural language search, while Code Security extends into SASTSASTStatic application security testing, analyzing source code or compiled code for vulnerabilities without running the application. It helps developers find problems before deployment., secret detection, and IDE plugins for developers. Originally launched in 2015, it continues to ship regular updates, with its most recent release 37 days ago.
Lacework FortiCNAPP is a cloud-native application protection platform providing visibility, compliance, and threat detection across cloud environments.
How Lacework FortiCNAPP helps
Which of my cloud accounts have a misconfiguration or vulnerability an attacker could reach right now?
scans AWS, Azure, and GCP configuration and workload data continuously and surfaces the findings through Explorer and the Alert Dashboard, filterable by severity and category
Is this alert something I need to act on tonight or can it wait?
generates an AI incident report and remediation guidance for composite alerts so the practitioner can judge severity and next steps without reconstructing the timeline by hand
Did this API key or credential get used somewhere it shouldn't have?
correlates cloud activity logs from CloudTrail and GCP/Azure log sources with known threat intelligence, including the FortiGuard IoC feed, and flags anomalous spikes such as compromised AWS key activity
What is actually running in my Kubernetes cluster and is any of it behaving abnormally?
attributes runtime observations to specific processes and evaluates EKS and GKE audit log violations against policy with low latency, showing which workloads triggered which rule
Does my code or pipeline contain a secret or vulnerable dependency before it ships?
runs SAST, secret detection, and software composition scans in CI/CD and the IDE, reporting exposed credentials or flawed packages against the build or pull request they came from
Which of my compliance policies are passing or failing across the whole environment, not just one account?
rolls up policy evaluation results into an aggregate compliance posture at the policy level so gaps in one account or cluster are visible against the full estate
Languages
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
Five scores for Lacework FortiCNAPP, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Lacework FortiCNAPP puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Website history
fortinet.com, every changeFortinet's home page and 39 more pages as they looked each month from August 2021 to October 2026: 51 renders, 6 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Coverage
Missing something? Tell us
What Lacework FortiCNAPP connects to, runs on and detects, read from its release notes and docs. So far: 1 new supported platform.
1 change, tracked since Nov 1, 2026.
-
Nov 12026
new Vulnerability assessment for Microsoft Azure Linux (CBL-Mariner)
Operating systems 2
Nothing first seen in this window. That doesn't mean Lacework FortiCNAPP shipped nothing, only that we found no record of it.
How we count
Read from 3 of 9 release notes and docs updates we hold for Lacework FortiCNAPP. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through Lacework FortiCNAPP's life, so an old integration can show a recent first-seen date.
Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.
Releases
9 entries
No entries match these filters.
- November 20263
- October 20261
- September 20263
- July 20262
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.