{
 "site": "aiendpointsecurityranked",
 "fixed": "2026-11-12",
 "criteria": [
  {
   "key": "sees",
   "name": "Sees agentic activity on the endpoint",
   "what": "An inventory of AI agents, skills, plugins, MCP servers and extensions across desktop apps, IDEs, command-line agents and browsers, as documented",
   "weight": 25
  },
  {
   "key": "stops",
   "name": "Stops the action",
   "what": "Blocking a harmful agent action before it completes, with the action types named, against detection or alerting after the fact",
   "weight": 25
  },
  {
   "key": "deploy",
   "name": "Deployment friction",
   "what": "Agentless or light deployment, operating systems covered, time to deploy as published",
   "weight": 15
  },
  {
   "key": "beyond",
   "name": "Beyond the endpoint",
   "what": "Coverage of browsers, cloud workspaces and SaaS-hosted agents in the same policy",
   "weight": 10
  },
  {
   "key": "policy",
   "name": "Policy and governance",
   "what": "The policy model, the audit trail, and integrations with EDR, SIEM and the identity provider",
   "weight": 10
  },
  {
   "key": "transparency",
   "name": "Transparency",
   "what": "Public documentation, a published price, published research",
   "weight": 10
  },
  {
   "key": "proof",
   "name": "Proof",
   "what": "Named customers, funding, independent analyst coverage",
   "weight": 5
  }
 ],
 "anchors": {
  "0": "none found on the read date",
  "7": "the most a vendor claim or vendor documentation alone can earn: detailed, specific, covering the whole criterion",
  "1-3": "mentioned, partial, or limited to one surface or one action type",
  "4-6": "documented and working, with gaps the documentation shows",
  "8-10": "detailed and confirmed by a second source (third-party write-up, or observed directly in public documentation, code or a release record)"
 },
 "rules": [
  "Every vendor is scored 0 to 10 on every criterion, whole numbers, from the evidence file only, by a scorer that is not told which vendor is the client.",
  "A vendor claim scores at most 7 until a second source confirms it (kind third-party or observed).",
  "None found scores 0 and is written \"none found on <date>\", never \"does not have\".",
  "Breadth facts (module counts, integration counts, headcount, funding) carry at most 10 percent of any ranking; they inform Proof only, which weighs 5.",
  "The total is the weighted sum of the scores divided by 10 (0 to 100 scale, published to one decimal).",
  "Ties break on the higher score on the heaviest criterion, then by name.",
  "Once the first score exists, no weight and no criterion changes. A score changes only when a sourced fact changes, logged with the fact."
 ],
 "situations": {
  "coding-agents": {
   "name": "An engineering organization where every developer runs coding agents with shell access",
   "weights": {
    "sees": 25,
    "stops": 35,
    "deploy": 15,
    "beyond": 5,
    "policy": 10,
    "transparency": 5,
    "proof": 5
   },
   "why": "A coding agent with a shell can delete, exfiltrate or install in seconds, so stopping the action before it completes matters most, followed by seeing which agents, MCP servers and extensions each developer runs."
  },
  "regulated-data": {
   "name": "A regulated company that must show which AI tools touch customer data",
   "weights": {
    "sees": 30,
    "stops": 15,
    "deploy": 5,
    "beyond": 15,
    "policy": 25,
    "transparency": 5,
    "proof": 5
   },
   "why": "An auditor asks for the inventory and the evidence trail, so seeing every AI tool and keeping a policy record with an audit log outweigh how fast the tool installs."
  },
  "lean-team-edr": {
   "name": "A lean security team with EDR in place and no view of AI agents",
   "weights": {
    "sees": 30,
    "stops": 20,
    "deploy": 25,
    "beyond": 5,
    "policy": 10,
    "transparency": 5,
    "proof": 5
   },
   "why": "A small team needs the missing view quickly without another heavy agent to run, so visibility and low deployment friction carry the most weight."
  },
  "staff-rollout": {
   "name": "A company rolling out an AI assistant and browser agents to all staff",
   "weights": {
    "sees": 20,
    "stops": 20,
    "deploy": 15,
    "beyond": 25,
    "policy": 10,
    "transparency": 5,
    "proof": 5
   },
   "why": "Staff-wide assistants and browser agents live in the browser and in SaaS as much as on the laptop, so coverage beyond the endpoint under one policy weighs most."
  },
  "board-30-days": {
   "name": "A CISO asked by the board for an inventory of AI agents within 30 days",
   "weights": {
    "sees": 40,
    "stops": 5,
    "deploy": 30,
    "beyond": 10,
    "policy": 5,
    "transparency": 5,
    "proof": 5
   },
   "why": "A 30-day inventory deadline rewards the widest view of agents on the most machines, deployed fastest; blocking can follow later."
  }
 },
 "source": "RUN.md (bay-ai-endpoint-security.md) section 3 site weights and section 4 situations, 12 Nov 2026; situation weights written in this commit before any vendor evidence or score",
 "scored_entities": "AI endpoint security tools"
}
