Customers performing regular security maintenance require methods to monitor vulnerability scan execution status and findings within VMware Telco Cloud Automation (TCA) and Harbor. Specifically, requirements include:
Forwarding Trivy scan status (Running, Completed, Failed) to a Syslog server.
Forwarding detailed vulnerability results (CVE-ID) to external monitoring platforms like Elasticsearch/Logstash.
Understanding supportability for third-party agents (Elastic Agent) on Harbor appliances and TKG clusters.
TCP5
TCA 3.2
CNF Harbor
Native end-to-end product workflows for parsing and forwarding specific vulnerability findings to external systems are not provided out-of-the-box and require environment-specific customization.
Operational Logs (Scan Status): Trivy runs as a containerized service within Harbor. Operational events (initiation, errors, DB updates) are emitted to stdout/stderr on the Pod.
Method: Use the TCA Fluent Bit Add-on to scrape container logs and forward them to a Syslog destination.
Vulnerability Data (Findings): Trivy does not write discovered CVEs to a log file; findings are stored in the Harbor database.
Method: Configure Harbor Webhooks to send a JSON payload to a listener (e.g., Logstash) upon the SCANNING_COMPLETED event.
Harbor on TKG (CNF):
Supported: Installing the Elastic Agent as a Kubernetes DaemonSet on the TKG workload cluster is supported as a customer-managed workload.
Responsibility: VMware supports the TKG platform stability; the customer is responsible for agent configuration and maintenance.
Harbor VM (Appliance):
Not Supported: Installing third-party binaries (RPM/DEB) directly onto the Harbor Appliance OS (Photon OS) is not supported.
Method: Use the native Audit Log Forwarding feature within the Harbor UI to send logs via Syslog (TCP/UDP 514).
Transport (VMware Scope): VMware supports the transmission of data via Fluent Bit or Webhooks to an external IP.
Ingestion/Parsing (Customer Scope): The logic required to parse JSON or Syslog streams (Grok filters) into Elasticsearch is a custom configuration outside the scope of standard product support.