Skip to main content
Challenge

Build a Hardware BOM and Firmware Vulnerability Audit Coordinator

Audit multi-node accelerator bill-of-materials and out-of-band management firmware against vulnerability databases. Hosted Claude identifies risky firmware revisions and drafts remediation batches.

EngineeringHosted by Vera
Challenge brief

What you are building

The core problem, expected build, and operating context for this challenge.

Audit multi-node accelerator bill-of-materials and out-of-band management firmware against vulnerability databases. Hosted Claude identifies risky firmware revisions and drafts remediation batches.

Infrastructure Security Engineer

Ingest standardized hardware inventory files listing host BMC, PCIe switch, and accelerator firmware versions.

Cross-examine firmware strings against synthetic security vulnerability advisory notices.

Send inventory vulnerability matches to hosted Claude to assess severity, exposure vectors, and operational downtime impact.

Export an audit dossier with prioritized maintenance windows and signed operator approval forms.

Security audit table with vulnerability severity tags and batch maintenance approval buttons.

Generate synthetic JSON inventories containing host UUIDs, BMC versions, firmware builds, and mock CVE identifiers. Starter examples below are synthetic. They are not downloaded records.

Anthropic Python SDK Employs Anthropic Python SDK to submit hardware BOMs and vulnerability metadata to hosted Claude for structured analysis.

crewai, anthropic, pydantic, requests. CrewAI provides role-based agent coordination between inventory auditing, vulnerability scoring, and maintenance scheduling. Hosted Claude API for technical vulnerability risk evaluation and batch remediation scheduling.

Submit runnable source, pinned dependencies, setup commands, a working interface, example outputs, and a recorded end-to-end demo. Include tests and an action log.

Flags all inventory records with firmware versions matching known mock security advisories.

Classifies firmware update urgency into Critical, Moderate, or Low based on network exposure.

Produces maintenance batch proposals that respect cluster minimum redundancy thresholds.

```json [ { "input": { "cluster_env": "training-cluster-1", "nodes": [ { "node_id": "node-101", "component": "BMC", "fw_version": "v1.2.0", "vulnerability_id": "MOCK-CVE-2025-101", "public_facing": false }, { "node_id": "node-102", "component": "BMC", "fw_version": "v1.4.2", "vulnerability_id": null, "public_facing": false } ] }, "expected_output": { "vulnerable_count": 1, "affected_nodes": [ "node-101" ], "priority_tier": "MODERATE", "scheduled_maintenance_window": "NEXT_PLANNED_DRAIN" } }, { "input": { "cluster_env": "serving-edge-2", "nodes": [ { "node_id": "edge-01", "component": "BMC", "fw_version": "v1.1.0", "vulnerability_id": "MOCK-CVE-2025-999", "public_facing": true } ] }, "expected_output": { "vulnerable_count": 1, "affected_nodes": [ "edge-01" ], "priority_tier": "CRITICAL", "scheduled_maintenance_window": "IMMEDIATE_ISOLATION" } } ] ```

Read-only compliance analysis. Does not apply firmware patches or reboot compute nodes. Use mock external writes. Require human review before any real deployment.

Rules

Participation guide

Read-only compliance analysis. Does not apply firmware patches or reboot compute nodes. Use mock external writes and human review.

Delivery guide

How work is evaluated

Evaluation

Flags all inventory records with firmware versions matching known mock security advisories. Classifies firmware update urgency into Critical, Moderate, or Low based on network exposure. Produces maintenance batch proposals that respect cluster minimum redundancy thresholds.

Submission format

Runnable source, pinned dependencies, setup commands, working interface, example outputs, recorded demo, tests, and action logs.

Datasets

Challenge datasets

Public datasets, plus the private datasets you have access to.

Evaluation rubric

How submissions are scored

These dimensions define what the evaluator checks and which criteria separate a passable run from a strong one.

Dimensions
4 scoring checks
Binary
1 pass or fail dimensions
Ordinal
3 scaled dimensions
Dimension 1

Complete workflow

Ingest standardized hardware inventory files listing host BMC, PCIe switch, and accelerator firmware versions. Cross-examine firmware strings against synthetic security vulnerability advisory notices. Send inventory vulnerability matches to hosted Claude to assess severity, exposure vectors, and operational downtime impact. Export an audit dossier with prioritized maintenance windows and signed operator approval forms.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 2

Correctness and evidence

Flags all inventory records with firmware versions matching known mock security advisories. Classifies firmware update urgency into Critical, Moderate, or Low based on network exposure. Produces maintenance batch proposals that respect cluster minimum redundancy thresholds.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 3

Review interface

Security audit table with vulnerability severity tags and batch maintenance approval buttons.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 4

Safe execution

Read-only compliance analysis. Does not apply firmware patches or reboot compute nodes.

Binary check

This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.

Learning goals

What you should walk away with

  • Ingest standardized hardware inventory files listing host BMC, PCIe switch, and accelerator firmware versions.

  • Cross-examine firmware strings against synthetic security vulnerability advisory notices.

  • Send inventory vulnerability matches to hosted Claude to assess severity, exposure vectors, and operational downtime impact.

  • Export an audit dossier with prioritized maintenance windows and signed operator approval forms.

Resources and assets

Reference links and supporting material

Dataset notes

Generate synthetic JSON inventories containing host UUIDs, BMC versions, firmware builds, and mock CVE identifiers. Supplied starter examples are synthetic, not source extracts.

Challenge setup

Configuration summary for this challenge.

Challenge input

Input details are not configured.

crewAI

Multi-agent orchestration framework

Evaluated output

No output checks are configured.

Evaluation checks
  • Ingest standardized hardware inventory files listing host BMC, PCIe switch, and accelerator firmware versio...
  • Flags all inventory records with firmware versions matching known mock security advisories. Classifies firm...
  • Security audit table with vulnerability severity tags and batch maintenance approval buttons.
Configured evaluation evidence
  • 2 public reference cases
Configured runtime
  • 1 configured tool

Summary shows the first task, up to three tools, and up to three evidence items. Open the technical recipe to view all configured items.

View technical recipe

Configured tools

Action Space
  • crewAI · Optional

Evaluation contract

  • Complete workflow · Weight 40
  • Correctness and evidence · Weight 30
  • Review interface · Weight 20
  • Safe execution · Weight 10

Reference cases

  • 2 public reference cases

Workflow tasks

No workflow tasks are configured.

Recipe freeze marker

No recipe freeze time is recorded.

Frequently Asked Questions about Build a Hardware BOM and Firmware Vulnerability Audit Coordinator