stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 3 Releases Wiki Activity
Files
417ef832025fb0ee05099479c3b0a7b685753c42
git.stella-ops.org/src/Concelier/__Libraries/StellaOps.Concelier.Connector.CertIn/AGENTS.md
master 417ef83202
Some checks failed
Docs CI / lint-and-preview (push) Has been cancelled
Details
Notify Smoke Test / Notify Unit Tests (push) Has been cancelled
Details
Notify Smoke Test / Notifier Service Tests (push) Has been cancelled
Details
AOC Guard CI / aoc-guard (push) Has been cancelled
Details
Concelier Attestation Tests / attestation-tests (push) Has been cancelled
Details
Export Center CI / export-ci (push) Has been cancelled
Details
Findings Ledger CI / build-test (push) Has been cancelled
Details
Findings Ledger CI / migration-validation (push) Has been cancelled
Details
Notify Smoke Test / Notification Smoke Test (push) Has been cancelled
Details
AOC Guard CI / aoc-verify (push) Has been cancelled
Details
Findings Ledger CI / generate-manifest (push) Has been cancelled
Details
Add unit and integration tests for VexCandidateEmitter and SmartDiff repositories 
- Implemented comprehensive unit tests for VexCandidateEmitter to validate candidate emission logic based on various scenarios including absent and present APIs, confidence thresholds, and rate limiting.
- Added integration tests for SmartDiff PostgreSQL repositories, covering snapshot storage and retrieval, candidate storage, and material risk change handling.
- Ensured tests validate correct behavior for storing, retrieving, and querying snapshots and candidates, including edge cases and expected outcomes.
2025-12-16 19:00:09 +02:00

2.7 KiB
Raw Blame History

AGENTS

Role

CERT-In national CERT connector; enrichment advisories for India; maps CVE lists, advisory text, mitigations, and references; non-authoritative for package ranges unless explicit evidence is present.

Scope

  • Discover and fetch advisories from the CERT-In portal; window by advisory code/date; follow detail pages.
  • Validate HTML or JSON; extract title, summary, CVEs, affected vendor names, mitigations; map references; normalize dates and IDs.
  • Persist raw docs and maintain source_state cursor; idempotent mapping.

Participants

  • Source.Common (HTTP, HTML parsing, normalization, validators).
  • Storage.Postgres (document, dto, advisory, alias, reference, source_state).
  • Models (canonical).
  • Core/WebService (jobs: source:certin:fetch|parse|map).
  • Merge engine treats CERT-In as enrichment (no override of PSIRT or OVAL without concrete ranges).

Interfaces & contracts

  • Aliases: advisory code if stable (scheme "CERT-IN") and CVE ids; if code is not stable, store as reference only.
  • References typed: bulletin/advisory/vendor/mitigation; deduped.
  • Affected omitted unless CERT-In publishes explicit version or fix details.
  • Provenance: method=parser; value=advisory code or URL; recordedAt.

In/Out of scope

In: enrichment, aliasing where stable, references, mitigation text. Out: package range authority; scraping behind auth walls.

Observability & security expectations

  • Metrics: shared concelier.source.http.* counters/histograms from SourceDiagnostics tagged concelier.source=certin capture fetch volume, parse failures, and map enrich counts.
  • Logs: advisory codes, CVE counts per advisory, timing; allowlist host; redact personal data if present.

Tests

  • Author and review coverage in ../StellaOps.Concelier.Connector.CertIn.Tests.
  • Shared fixtures (e.g., PostgresIntegrationFixture, ConnectorTestHarness) live in ../StellaOps.Concelier.Testing.
  • Keep fixtures deterministic; match new cases to real-world advisories or regression scenarios.

Required Reading

  • docs/modules/concelier/architecture.md
  • docs/modules/platform/architecture-overview.md

Working Agreement

    1. Update task status to DOING/DONE in both correspoding sprint file /docs/implplan/SPRINT_*.md and the local TASKS.md when you start or finish work.
    1. Review this charter and the Required Reading documents before coding; confirm prerequisites are met.
    1. Keep changes deterministic (stable ordering, timestamps, hashes) and align with offline/air-gap expectations.
    1. Coordinate doc updates, tests, and cross-guild communication whenever contracts or workflows change.
    1. Revert to TODO if you pause the task without shipping changes; leave notes in commit/PR descriptions for context.