Below is a sample output from a server running virtual machines. The output uses the SPDX V3.1 standard that includes hardware, supply chains, operations, AI, and safety. A typical audit includes 1,000s of nodes for analysis and review.
The following sample audit output compares a few processes that have changed between read 1 and read 2. Output is quickly generated based on your defined policy. By comparing the output from read 1 & 2, you can identify operational system changes.
Avoid speculation and respond in near real time to address actual threats.
The SPDX (System Package Data Exchange) standard is used to assemble the SysAuditor supply chain inspection documents. This structure includes detailed metadata about system events or activities—often related to process or resource monitoring in supply chain or system security contexts.
type: "supplychain_InspectionAction"
This denotes an event or process action in the supply chain inspection workflow, which can document the verification, audit, or status of digital components.
spdxId:
The unique SPDX identifier marks this record or entity as distinct within a supply chain ecosystem. It supports traceability and linkage between software, hardware, and audit elements for compliance and provenance documentation.
creationInfo:
Metadata field for when and how the entry was created. This is vital for transparency and audit trails, as it tracks the time and the responsible party. trazable+1
type: "DictionaryEntry" with key/value pairs
These represent specific attributes or properties of the inspected entity. For example:
"Name": "kworker/u50:3-flush-252:0" is likely identifying a Linux kernel worker thread involved in I/O operations or memory tasks.
"voluntary_ctxt_switches": "3383" logs the number of voluntary context switches performed, which is important data for performance, anomaly detection, or cybersecurity monitoring.