Get desktop application:
View/edit binary Protocol Buffers messages
Affects is used to identify the affected components.
Used in: ,
Required. Root component that is affected
Optional. List of sub-components that are affected
AttackTactic is used to identify the tactic used in an attack. Typically this refers to identifier on the MITRE ATT&CK framework.
Used in:
Unique identifier for the tactic
Name of the tactic
Description of the tactic
AttackTechnique is used to identify the technique used in an attack. Typically this refers to identifier on the MITRE ATT&CK framework.
Used in:
Unique identifier for the technique
Name of the technique
Description of the technique
Component is used to identify the affected component.
Used in:
Required. Name of the component
Required. Version of the component
Additional properties
Experimental. Component details based on type
Confidence levels in finding
Used in: ,
Network Connection information
Used in:
Destination address, either hostname or ip.
Destination port
Optional: Source address, either hostname or ip.
Optional: Source port
Protocol used in the connection
Protocol defines the protocol used in the connection. Decimals are equivalent to the protocol numbers assigned by IANA. See https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml
Used in:
Unspecified protocol, does not correspond to any real protocol.
Internet Control Message Protocol.
Transmission Control Protocol.
User Datagram Protocol.
Experimental. Details about the container that lead to the finding. Only used for containerized environments.
Used in: ,
Container name
Container image URI (e.g. marketplace.gcr.io/google/ubuntu1804:latest)
Container image digest
Experimental. Evidence shares details about the facts that lead to the finding
Used in: ,
Attack tactic used
Attack technique used
Confidence in the threat
Details about the resource that lead to the finding
Additional properties specific to this evidence
Experimental. File information
Used in: ,
Absolute path to the file
File size in bytes
MD5 hash of the file
SHA256 hash of file
Optional. File content.
Experimental. File-specific component details
Used in:
Path to the file
File hash for version tracking
File format or type
File size in bytes
Core information about the finding
Used in:
Category of the finding
Severity of the finding
How confident the source is in this finding
Detailed description of the finding
External references (e.g., CVE, CWE, OWASP)
Additional properties specific to this finding type
Used in:
FindingDocument is a wrapper message that can hold either a VulnerabilityExchange or a FindingExchange document.
Used in:
FindingExchange are used for sharing information about findings across systems. Mondoo uses this format as a main mean to store detected finding information.
Used in:
Required. Unique identifier for this finding.
Optional. External reference identifier from the original data source. We expect this to be a unique identifier in the original data source.
Mondoo Resource Name (MRN). This is read-only and is assigned by Mondoo.
Optional. Result group identifier. Used to group related findings.
Required. Brief summary of the finding (e.g. "SQL Injection in endpoint")
Optional. Detailed information about the finding
Required. Timestamp when the finding was first detected
Optional. Timestamp when the finding was last seen
Optional. Timestamp when the finding was remediated
Required. Current status of the finding
Required. Information about the source that produced this finding
Required. List of affected components
Optional. Technical evidence
Optional. Available remediation options
FindingsUploadRequest is the file format uploaded to the ingest bucket for findings uploads. It contains all findings along with metadata needed by the processor.
Experimental. Details about Kubernetes resource. Only used for Kubernetes environments.
Used in:
Affected pods
Affected nodes
Kubernetes node information
Used in:
Node name
Unique identifier for the node eg. EC2 instance ID
Kubernetes pod information
Used in:
Pod name
Pod namespace
Container information
Experimental. Details about the process that lead to the finding
Used in:
Process name or command line as displayed in the process list
Process file information, eg. python binary
For scripts, the script file information
The process ID.
User
The parent process.
Rating is used to provide a score for the vulnerability. Deprecated: use Severity instead
Used in:
Required. Source of the rating
Optional. Score of the rating Note: To not get precision errors we need float
Optional. Severity of the rating, e.g. "high", "medium", "low"
Optional. Vector of the rating
Optional. Scoring method of the rating
Reference is used to provide additional information about the vulnerability.
Used in: ,
Optional. ID of the reference
Required. Name of the reference
Required. URL of the reference
Type of reference (e.g., "CVE", "CWE")
Additional reference metadata
Windows Registry Key information
Used in:
Path to the registry key (e.g., "HKLM\\SOFTWARE\\Microsoft\\Windows")
Name of the value (empty string for default value)
The actual data
Remediation is used to provide a fix for the vulnerability.
Used in: ,
The category of the remediation
Required. Summary of the remediation
Optional. Instruction details of the remediation
Fix type like 'terraform', 'ansible', 'package'
Optional. ID of the fix
Optional. URL to the fix
The category type of the remediation
Used in:
ScoringMethod is used to identify the scoring method of the rating.
Used in: ,
This is the equivalent of the Ubuntu scoring method from OSV: https://ossf.github.io/osv-schema/#severity-field
Severity is used to provide a score for the vulnerability. This message is backwards compatible with the Rating message.
Used in:
Required. Source of the rating
Optional. Score of the rating Note: To not get precision errors we need float
Optional. Severity of the rating, e.g. "high", "medium", "low" Deprecated: Use rating instead
Optional. Vector of the rating
Optional. Scoring method of the rating
Required. Severity rating of the rating
SeverityRating is used to identify the severity of a finding.
Used in:
Critical risk severity
High risk severity
Medium risk severity
Low risk severity
No risk severity
Source is used to identify the source of the vulnerability.
Used in: , , ,
Required. Name of the source
Optional. URL of the source
Status is used to identify the status of the vulnerability.
Used in: ,
Unspecified status
Vulnerability is not affected
Vulnerability is affected
Vulnerability is fixed
Vulnerability is under investigation
Not a real issue
Accepted risk
Experimental. User information
Used in: ,
User ID
User name
Additional properties
VulnerabilityDetails are used to provide detailed information about the vulnerability.
Used in:
Optional. Description of the vulnerability
Optional. Recommendation for the vulnerability
Optional. Workaround for the vulnerability
Time the vulnerability was created
Time the vulnerability was published
Time the vulnerability was last updated
VulnerabilityExchange are used for sharing information about vulnerabilities across systems. Mondoo uses this format as a main mean to store detected vulnerability information. The same document is generated independently from the source.
Used in:
Optional. Externally provided ID from the original data source
Required. CVE or Advisory ID
Optional. Mondoo Resource Name (MRN)
Required. Summary of the vulnerability
Optional. List of aliases for the vulnerability
Optional. related vulnerabilities, e.g. CVE-2024-123456
Optional. upstream vulnerabilities, e.g. CVE-2024-123456
Optional. Detailed information about the vulnerability
Required. Source of the vulnerability
Optional. List of severities for the vulnerability In OSV, this is called a Severity TODO: switch to new Severity message
Optional. Time the vulnerability was first seen
Optional. Time the vulnerability was remediated
Required. List of affected components
Required. Status of the vulnerability
Optional. List of references for the vulnerability
Optional. List of available remediation
Optional. Database specific information DatabaseSpecific holds additional information about the vulnerability as defined by the database from which the record was obtained. See https://ossf.github.io/osv-schema/#database_specific-field.
Optional. Technical evidence