Skip to content

IRMind v0.4.2

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 14 Nov 13:56
· 307 commits to main since this release

IRMind v0.4.2 — Case budgets and Kubernetes investigations

Format impact: current case contracts change. The expanded common-event
vocabulary changes the mapped target-contract digest. Cluster-aware sources add
explicit acquisition context and optional physical metadata; new case allocations
are signed in creation/change receipts. Export V7 framing and seal challenges
are unchanged, but their current profile/envelope vectors reflect the new
contract. Retain the creating executable to open, verify or export an older
case, or re-ingest verified originals into a new case. No automatic migration
is provided.

All modules and methods remain experimental and tested with synthetic data.
H5 was accepted by the analyst after a real DeepSeek greeting; the remaining
manual procedure details and validation of a real connector remain pending.

Kubernetes investigation methods and verified originals

  • Include k8s-cluster-compromise and k8s-workload-compromise, bringing the core
    catalog to 15 skills. Both cover source collection, typed local queries,
    original-field review, coverage gaps and conditional findings. Their scripted
    synthetic episodes confirm findings and verify, seal and independently verify
    exported cases; expected answers remain evaluator-only.
  • Add explicit raw_records view="original" for bounded, guarded source facts.
    Local source roots require analyst-origin authorization. Reads verify source
    bytes, the frozen decoder/context and the signed decoded-record commitment;
    indexed reads remain the default. No network, decoded cache or spool is used.
  • Add the separate Falco Kubernetes-audit mapping and explicit privilege facts.
    Kubernetes protocol-upgrade responses remain unknown outcomes, rather than
    evidence that a command ran successfully.
  • Cover native audit logs and managed EKS, GKE and AKS exports. No live Kubernetes
    API connector, remote model default or implicit cloud-identity link is added.

Fixed

  • Align the isolated EVTX fuzz workspace with the current helper version and
    check resolution of all four locked workspace graphs during CI. Keep the
    existing decoder and protocol ASAN campaign budgets.

Managed Kubernetes export transports

  • Decode EKS CloudWatch GetLogEvents and AKS kube-audit/kube-audit-admin
    resource-log envelopes, preserving original transport fields and the decoded
    audit Event with real outer-row provenance.
  • Include separate hash-pinned EKS/AKS tables and explicit cluster confirmation.
    Reject contradictory source claims and request confirmation for new clusters.
    Detect GCP/GKE LogEntry arrays produced by gcloud as well as NDJSON.
  • Format impact: additional source-format/mapping identities; native Event
    decoding, signed envelopes, physical schemas, seals and exports do not change.

Microsoft Entra source coverage

  • Add experimental, default native SignInLogs and AuditLogs decoding and
    identified mappings for Azure Monitor resource logs and Log Analytics object
    rows, including non-interactive and service-principal sign-ins.
  • Preserve nanosecond time and original dynamic/MFA/Conditional Access fields;
    map explicit outcome and tenant-scoped actor/target roles. Update the Azure
    skill and its complete scripted episode to use native semantic queries.
  • Format impact: new parser/mapping identities, with no envelope, schema,
    seal or export framing change.

Network interpretation

  • Classify native Zeek and Suricata records with typed endpoint roles, protocol
    fields, explicit status outcomes and unconfirmed source alerts. Update the
    network skill's synthetic episode to query category, outcome and role.
  • Network mapping identities and their current logical golden projections change;
    source decoders, signed envelopes, physical schemas and export format do not.

GCP Cloud Audit and GKE interpretation

  • Add a default, experimental Cloud Audit JSON/NDJSON source decoder and bundled
    service/status mappings, sharing explicit cluster confirmation with GKE.
    Preserve nanosecond time and original fields; distinguish reported caller,
    target resource and source/destination endpoints. Redacted IPs remain unknown.
  • Keep missing RPC status unknown and classify project-policy operations only
    from documented exact method names. Validate GKE namespace/resource paths and
    keep zonal locations distinct from regions. Unknown services retain coverage gaps.
  • Update the GCP service-account skill and its scripted episode to use native
    IAM/outcome/role filters, with independent evaluator-only HuntEval answers.
  • Format impact: no additional envelope, export framing or seal change.

Kubernetes and Falco source modules

  • Add separate experimental native Kubernetes audit and Falco JSON decoders, selected by the bounded detection registry. Original fields, nanosecond timestamps and actual offsets are retained; mappings remain independent.
  • Ask for required cluster acquisition context in the TUI, with explicit per-file or batch confirmation. CLI and /ingest --cluster use the same typed, signed context. No identity is inferred from the machine or path, and no live API access is added.
  • Include hash-pinned Kubernetes and Falco table mappings: explicit API outcomes, actor/impersonation roles, namespaced target resources, and unconfirmed source alerts. Cluster search projects validated fields instead of whole request/response bodies.
  • Include synthetic fixtures, detection-matrix coverage, malformed/oversized-record regressions, cluster-confirmation keyboard tests and signed ingest/rebuild/seal/export coverage.
  • Format impact: no additional format change beyond the cluster/common vocabulary extensions described below.

Cluster-qualified common events

  • Extend the current common event vocabulary with bounded orchestrator,
    container, group and privilege fields and cluster/namespace-qualified entities.
    Raw producer cluster IDs remain separate from acquisition identity.
  • Add an exact cluster query filter, signed partition pruning and row filtering
    inside overflow buckets. Hash verification and all query limits remain intact.
  • Cluster artifacts carry an explicit optional column/metadata extension;
    non-cluster Parquet files retain their physical bytes. Unmapped cluster sources
    retain originals and commitments without projecting arbitrary request bodies.
  • Format impact: the expanded common vocabulary changes the mapped target-contract
    digest and current profile/envelope/export vectors. V7 framing and seal
    challenges are unchanged. Use the creating version for another contract, or
    re-ingest verified originals into a new case; no migration is introduced.

Kubernetes ingestion foundation

  • Bind explicit, bounded cluster acquisition context to source manifests,
    decoded-record commitments and reconstruction. Cluster claims cannot grant
    permissions or silently replace analyst-confirmed identities.
  • Add deterministic cluster partitions with 64 ordinary values by default,
    a maximum of 1,024 and signed overflow buckets. Raw cluster identifiers never
    become directory names.
  • Format impact: current source manifests and record-set commitments gain an
    optional cluster-context extension; records carrying cluster context include
    it in their canonical hash. Sources without context retain their bytes.

Case allocations

  • Add signed defaults for new cases in /settings limits and signed per-case
    token, tool-call and reserved cloud-byte allocations in /budget. Organization
    ceilings remain mandatory; increases need explicit Analyst confirmation.
  • Use 2,000,000 tokens and 1,000 calls by default, retaining all fixed maxima and
    existing cloud-transfer controls. Existing policy files are not rewritten.
  • Show consumption and 80% warnings, and retain completed work with a tool-free
    or local summary when an allocation is exhausted. Missing provider usage is
    labeled unavailable; costs are shown only when supported by usage/pricing.
  • Format impact: case creation records include the initial allocation and later
    changes use CaseBudgetChanged receipts. Existing signed-entry and export V7
    framing are unchanged. Cases without a recorded allocation require explicit signed confirmation in
    /budget before new model/tool work; recorded consumption is retained.

Download each binary with SHA256SUMS and its Sigstore bundle. Verify the exact tag/workflow identity and GitHub build provenance before installation; see verification instructions. Known co-observation/query performance follow-ups remain in issue #37. macOS notarization and Windows Authenticode are not provided; operating-system warnings may appear.