CISA KEV Asset Remediation Report
Pricing
from $60.00 / 1,000 kev asset potential matches
CISA KEV Asset Remediation Report
Track CISA KEV remediation. Open Input → leave defaults → Start (1 asset + deadline alert ≈ USD 0.01–0.03/asset): https://console.apify.com/actors/6gr3TidBKn8MHu7LE/input From USD 0.
Pricing
from $60.00 / 1,000 kev asset potential matches
Rating
0.0
(0)
Developer
naoki anzai
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
18 days ago
Last modified
Categories
Features
Share
What you get: one row per conservative match between your asset inventory and the official CISA Known Exploited Vulnerabilities catalog, with the CVE, vulnerability name, CISA required action, due date, ransomware-use flag and match evidence (optional deadline alerts, portfolio report and export).
Sample output from a real run (2026-10-18, the first-run JSON below, 2 rows):
| assetId | cveID | vulnerabilityName | dueDate | ransomware use | matchEvidence |
|---|---|---|---|---|---|
| web-prod-01 | CVE-2021-44228 | Apache Log4j2 Remote Code Execution Vulnerability | 2021-12-24 | Known | vendor_exact, product_exact |
| web-prod-01 | CVE-2021-45046 | Apache Log4j2 Deserialization of Untrusted Data Vulnerability | 2023-05-22 | Known | vendor_exact, product_exact |
That run was 2 × kev-asset-potential-match ($0.06) = $0.12. A potential match is a review signal, not proof the asset is vulnerable.
Open Input (paste the JSON below → Start)
Paid first run ≈ USD 0.12 for 1 asset (Apache Log4j2 → 2 × kev-asset-potential-match at $0.06; deadline alerts are $0.35 each and are off here). The Console defaults use initialRunMode: "baseline_only", which saves a free baseline with no billable rows, so paste this JSON (emit_backfill) and Start.
{"assets": [{"assetId": "web-prod-01","vendor": "Apache","product": "Log4j2","versions": ["2.14.1"],"environment": "production"}],"monitorKey": "kev-first-run","initialRunMode": "emit_backfill","generateReport": false,"emitPotentialMatches": true,"includeDeadlineAlerts": false,"emitUnchanged": false,"maxChargeUsd": 0.15,"dryRun": false,"maxRetries": 1,"maxBackoffMs": 3}
Store Quickstart
Run the bounded paid first-run JSON above first; keep report/export options off unless needed.
{"assets": [{"assetId": "web-prod-01","vendor": "Apache","product": "Log4j2","versions": ["2.14.1"],"environment": "production"}],"monitorKey": "kev-first-run","initialRunMode": "emit_backfill","generateReport": false,"emitPotentialMatches": true,"includeDeadlineAlerts": false,"emitUnchanged": false,"maxChargeUsd": 0.15,"dryRun": false,"maxRetries": 1,"maxBackoffMs": 3}
- Supply one or more assets that your team is authorized to review. Each asset needs
vendor+product, or a CPE 2.3 value. - Run the first live check with
initialRunMode: "baseline_only". It validates the complete CISA catalog, saves the snapshot, and emits 0 rows / 0 charge. - Reuse the same
monitorKeyfor later checks. Useemit_backfillfor the first comparison that should deliver changed matches.
The smallest useful trial is:
{"assets": [{ "assetId": "web-prod-01", "vendor": "Apache", "product": "Log4j2", "versions": ["2.14.1"] }],"monitorKey": "trial-kev-portfolio","initialRunMode": "baseline_only","generateReport": true,"emitPotentialMatches": true,"includeDeadlineAlerts": true,"deadlineWithinDays": 30,"emitUnchanged": false,"emitExport": false,"dryRun": false,"maxChargeUsd": 0}
Example 1: production inventory
{"assets": [{ "assetId": "web-prod-01", "vendor": "Apache", "product": "Log4j2", "versions": ["2.14.1"], "environment": "production" },{ "assetId": "edge-01", "vendor": "Example Vendor", "product": "Example Appliance", "versions": ["4.2"] }],"monitorKey": "production-kev-watch","initialRunMode": "emit_backfill","generateReport": true,"emitPotentialMatches": true,"includeDeadlineAlerts": true,"deadlineWithinDays": 45,"emitUnchanged": false,"emitExport": true,"dryRun": false,"maxChargeUsd": 30}
Example 2: CPE-backed inventory
{"assets": [{"assetId": "linux-image-01","cpe": "cpe:2.3:a:example:appliance:4.2:*:*:*:*:*:*:*","product": "Example Appliance","vendor": "Example","versions": ["4.2"],"environment": "staging"}],"monitorKey": "staging-kev-watch","initialRunMode": "baseline_only","generateReport": true,"emitPotentialMatches": true,"includeDeadlineAlerts": true,"deadlineWithinDays": 14,"emitUnchanged": false,"emitExport": false,"dryRun": false,"maxChargeUsd": 0}
Example 3: deterministic dry run
{"assets": [{ "assetId": "demo-01", "vendor": "Apache", "product": "Log4j2", "versions": ["2.14.1"] }],"monitorKey": "dry-run-demo","initialRunMode": "emit_backfill","generateReport": true,"emitPotentialMatches": true,"includeDeadlineAlerts": true,"deadlineWithinDays": 30,"emitUnchanged": false,"emitExport": true,"dryRun": true,"maxChargeUsd": 50}
Dry-run output is deterministic and does not call the network, save state, or charge events.
Use with Apify MCP
Exact actor: taroyamada/cisa-kev-asset-remediation-report
Sample input JSON:
{"assets": [{"assetId": "web-prod-01","vendor": "Apache","product": "Log4j2","versions": ["2.14.1"],"environment": "production"}],"monitorKey": "kev-first-run","initialRunMode": "emit_backfill","generateReport": false,"emitPotentialMatches": true,"includeDeadlineAlerts": false,"emitUnchanged": false,"maxChargeUsd": 0.15,"maxRetries": 2,"maxBackoffMs": 3,"dryRun": false}
Security and vulnerability-management teams provide a bounded asset inventory, the actor compares it with the official CISA Known Exploited Vulnerabilities Catalog, and the output is a source-linked review queue containing conservative potential matches, CISA required actions, due dates, deadline signals, and optional exports.
The first baseline_only run and every unchanged run produce zero rows and zero charge.
Every match is labeled potential_match and review_required. The actor never asserts that an asset is vulnerable, compromised, exploitable, compliant, or remediated.
Output
kev_remediation_report is emitted first. It summarizes changed potential matches. kev_asset_potential_match carries the asset join, CISA CVE, vendor/project, product, description, requiredAction, dueDate, source URL, and explicit review labels. kev_deadline_alert carries the due-date window or due-date change reason. kev_remediation_export lists the stable keys included in the handoff.
The CISA requiredAction and dueDate fields are copied as source evidence. versionMatchStatus is not_assessed_from_cisa_catalog; the CISA feed does not provide enough inventory mapping to prove version applicability.
Pricing and billing safety
| Event | Price | When it is charged |
|---|---|---|
kev-asset-potential-match | $0.06 | A changed conservative potential match is delivered |
kev-deadline-alert | $0.35 | A changed/new match has a due-date review signal |
kev-remediation-report | $12.00 | A changed portfolio report is delivered |
kev-remediation-export | $8.00 | An export handoff is delivered |
There is no start event. A baseline or unchanged run is always 0 rows and 0 charge. Rows are delivered in order while they fit maxChargeUsd and your run's "Max cost per run"; rows that would exceed either limit are skipped (not charged) and explained in a free run_summary row, and the run still succeeds. If no row fits, the baseline is not saved so the rows are offered again after you raise the limit. Unknown event names, duplicate CVEs, invalid catalogs, state failures, and missing charge proof fail closed.
Compliance and interpretation guardrails
- Official source: CISA KEV JSON only. No API key is required.
- The buyer must supply an authorized, bounded inventory. The actor does not scan networks or discover assets.
- Every match means
potential_matchandreview_required, never a confirmed finding. - Do not use the output as a statement of vulnerability, compromise, exploitability, compliance, legal status, remediation completion, or security advice.
- Review the current official CISA record and internal evidence before assigning work.
- The actor is not affiliated with or endorsed by CISA or the U.S. government.
See also
For adjacent review workflows, compare this actor with the package portfolio upgrade report and product safety market-action portfolio report. They use similar baseline, change detection, report-first, and fail-closed delivery patterns for different source domains.
See docs/source-compliance.md, docs/integration-guide.md, and docs/sample-output.json for the operational contract.