Material Security
Map Sensitive File Sharing in Drive and Simplify Customization in Material commercialThe section your link pointed to isn't on Material Security's page any more, so we've brought you to the top.
Material Security is an email security platform that uses AI to detect and prevent advanced threats like phishing, malware, and data exfiltrationdata exfiltrationMoving data out of a system or organization without authorization. It can happen through network transfers, removable media or other channels..
Summary
Material Security is a commercial 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. platform that secures data stored in email and Drive by finding where sensitive content is exposed and giving teams a way to act on it. It runs as a service connected to a company's Google Workspace or similar environment, aimed at security and IT teams responsible for SaaS and identity risk rather than end users. Its dashboard maps how sensitive Drive files are shared — publicly, externally, company-wide, or with trusted partners — so an analyst can check whether source code or M&A documents have leaked outside the company, and its plain-English file search helps during offboarding when someone needs to find what a departing employee still has access to. Custom detections for email and files are built and edited from one screen rather than several.
Material Security is an email security platform that uses AI to detect and prevent advanced threats like phishing, malware, and data exfiltration.
Material Security publishes no documentation we track, so the description above is written from general knowledge rather than the vendor's own words.
How Material Security helps
Which sensitive Drive files are shared outside the company right now?
maps every sensitive file's sharing state — public, external, company-wide, or trusted external — with drill-down by content category, so an analyst can check source code or M&A documents for exposure without building a query
What does a departing employee still have access to?
lets an analyst describe what they're looking for in plain English and returns the matching Drive files the employee can reach, standing in for a structured search during offboarding
Which files are over-shared and what should happen to them?
attaches remediation actions directly to the file's issue or detail page, with configurable notification order and grace periods, so fixing exposure doesn't require a separate trip to the detection page
What exactly happened to a given file, and when?
keeps a per-file audit log of every security action taken against it, giving a timeline an analyst can check without reconstructing events from separate systems
Which alerts are actually passwords versus payroll data versus SSNs?
splits what used to be one combined sensitive-content detection into separate categories per data type, so the risk view shows which specific kind of exposure fired
Can an agent read or change an issue without leaving a trace?
requires the agent to authenticate as the calling user, hides write actions like patching an issue from users without write access, and logs every tool call — parameters, caller identity, and outcome — to the same audit log as UI and API activity
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 Material Security, 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 Material Security 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…
Releases
6 entries
No entries match these filters.
- October 20262
- September 20261
- August 20262
- July 20261
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.