---
title: "AI cybersecurity analyst — runs locally | AgentVUE"
description: "Hire an AI cybersecurity analyst that runs locally on your machine: full inventory of your systems and repositories, findings ranked against published advisories, a report you review before anything is applied. From €49/month."
canonical: "https://agentvue.ai/ai-employees/cybersecurity-analyst/"
language: "en"
---
AI employees

# AI cybersecurity analyst — runs locally.

The role that reads and explains: what is vulnerable on your machine, which version fixes it, what to treat first — in plain language, before anything is applied.

[Get AgentVUE→](/pricing/)[See the cybersecurity track](/cybersecurity/)

-   Read-only by design
-   Local inventory
-   Plain-language report
-   From €49/month

Cyber analyst · ReportRead-only

This run**What is exposed**

-   Critical**PHP 8.4**
-   High**Node.js**
-   Medium**2 packages**
-   Report**Dated · local**

InventoryMatchExplainHand over

Findings**5**Explained**5**Applied**0**

Read-only. Nothing is applied.

What it does

## It reads the machine and explains it.

Inventory, match, rank and explain. The analyst stops at the report.

The AI cybersecurity analyst answers the question every small team postpones: what is actually exposed on this machine, and what matters first? It holds the recurring reading work — inventory the machine and the repositories, compare the versions found against published advisories, rank the findings and explain them in plain language.

The analyst is deliberately read-only. It reports; it does not apply. When you decide something must be fixed, the engineer role takes over — a reasoned proposal, a snapshot, the change applied with your approval and a post-check. Same licence, two roles, one loop.

What you get

## What lands on your desk.

A ranked report you can read, share and act on.

### An inventory you can actually use

Installed packages, services, open ports, users, scheduled tasks, configuration drift and the dependency SBOM — collected from your machine and your repositories in one pass.

### Prioritised findings

Versions found are compared against published advisories: npm, PyPI, vendor advisories and CISA alerts. Recent example of the newsflow it keeps up with: Node.js shipped security releases on 21 October 2026 (26.12.1, 24.22.1, 22.23.4), including a Brotli decoder out-of-bounds write enabling code execution (CVE-2026-111497) and two TLS certificate hostname bypasses; CISA KEV gained six new entries on 20 October 2026, including four Plex CVEs.

### Advisory reading in plain language

For each finding: what it is, why it matters for this machine, which version fixes it and what to treat first. Short sentences, concrete nouns — a report a non-specialist can act on.

### A report the human reviews before anything is applied

The analyst stops at the report. Nothing changes on your machine from its output until you — or the engineer role, with your approval — decide to act.

[Node.js — October 2026 security releases](https://nodejs.org/en/blog/vulnerability/october-2026-security-releases)

In the app

## A report you can read.

Severity, affected version and a plain-language explanation on one page.

![Read-only AgentVUE cybersecurity report ranking 64 findings by severity, with advisory counts, exposure and a plain-language summary.](/images/product/cybersecurity.webp)

**Cyber analyst — ranked report**Severity-ranked findings, advisory counts and a plain-language executive summary.

How a run goes

## Four steps. All on your machine.

The analyst never applies a change.

AI cybersecurity analyst — runs locally. — runPlay the loop

01**Inventory first**02**Prioritised findings**03**Your review, not an auto-fix**04**The report stays with you**

### Inventory first

The workstation maps your machine and your repositories: installed packages, services, open ports, users, scheduled tasks, configuration drift, dependency SBOM.

### Prioritised findings

Collected versions are compared against published advisories at run time. What is exposed and internet-facing comes first; the internal nice-to-have comes later.

### Your review, not an auto-fix

The report waits for you. You read, you decide, and fixes — if you want them applied — go through the engineer role with your approval.

### The report stays with you

A dated local export, ready for a client questionnaire or an internal review. Nothing leaves the machine unless you export it.

Control

## It reads. It does not apply.

Fixes go through the engineer role.

Where you stay in control

### Read-only by design.

The analyst inventories, matches and explains. Fixes go through the engineer role, with your approval.

TaskRead-onlyAction

It reports. It does not apply.

Start here

## Start with the reading.

Pick your plan, install, and let the first inventory tell you what needs attention.

[Get AgentVUE→](/pricing/)[See the cybersecurity track](/cybersecurity/)

Built with AgentVUE

## The workstation builds itself.

The same agents that run the role run AgentVUE. You are buying the machine that already does the work.

[See the showcase](/showcase/)

![AgentCode showing a GitLab work item to build the one-page service site, the AgentVUE Suite sidebar and an open positioning.md draft.](/images/product/agentcode.webp)

**AgentVUE builds AgentVUE**AgentCode building the AgentVUE site from a GitLab work item, with the Business Kit in the sidebar.

Keep reading

## Keep reading

The role in context — same licence, same machine.

[What is an AI employee?](/ai-employees/)[The cybersecurity track](/cybersecurity/)[The engineer role: fixes applied with your approval](/ai-employees/cybersecurity-engineer/)[Plans and pricing](/pricing/)

Questions

## AI cybersecurity analyst questions, answered

The scope, the report, the approvals and the price.

Is the AI cybersecurity analyst read-only?

Yes, by design. It inventories, matches and explains; it applies nothing. Fixes go through the engineer role, and only with your approval.

What exactly does it look at?

Your machine and your repositories: installed packages, running services, open ports, users, scheduled tasks, configuration drift and the dependency SBOM. The inventory is collected on your disk, in one pass.

How current are the findings?

Findings are matched against published advisories when the run executes — npm and PyPI advisories, vendor advisories, CISA alerts and KEV entries. The comparison runs against your real installed versions, not a self-declared list.

What is the difference with the AI cybersecurity engineer?

The analyst reads and explains; the engineer prepares and applies. The analyst's report is the input to the engineer's fix — and both run on the same machine under the same licence.

Will I understand the report?

That is the job. Each finding states what it is, why it matters for this machine, which version fixes it and what to treat first — in plain language, without a jargon wall.

What does it cost?

One licence covers the whole workstation: Pro €49, Max €99, Ultra €199 per month billed yearly, or €33/€66/€123 per month with three years prepaid and one year free. The details are on the pricing page.

Next step

## Start with the reading.

Pick your plan, install, and let the first inventory tell you what actually needs attention.

[Get AgentVUE→](/pricing/)[Talk to the founder](/consultancy/)
