Create an Audit Log wizard

[jpower432]

Workflow Name

audit_log_builder

Description

Create tooling, skills, and prompts for guided Audit Log artifact creation. This should be able to use the inline mappings to explain to the user why a certain criterion exists.

Gemara Schema Definition

#AuditLog

Mode

artifact

Proposed Wizard Steps

A turn-based HITL flow for log population:

1. Prompt user for the Component ID and owner information (agent could be listed as the author in the metadata, while user is listed as accountable/responsible)

2. Load the Catalog or Policy and optional MappingDocument to establish definition of good or criteria

3. Prompt user for evidence links. Perform an initial scan of these to verify they exist. Possibly supported by Add config parser gemara-mcp#9.

4. Compare the provided evidence against the criteria. If a criterion lacks evidence, it flags a Gap. Supported by Gap Analysis Support #2

5. Present evidence and gaps back to the user. Prompt the user specifically for the missing items.

6. Generate the #AuditLog artifact, validate it against the schema, and present back to the user final verification.

Mapping References

• Criteria is mapped as Catalogs or Policy.
• Mapping references are supplied as evidence artifacts to support audit result entries at the evidence field

Additional Context

No response

[jpower432]

Making a note here, it would be interest to see if this skill can be leveraged to enhance the outcome - https://github.com/david-a-wheeler/secure-dependencies/tree/main