Network/Host Vulnerability Management

Please summarise or attach your network vulnerability management processes and procedures?

We have a structured process in place for identifying, assessing, and addressing network and host-level vulnerabilities within our infrastructure.

• Vulnerability Scanning:
  We use Google Cloud Security Command Center (SCC) to perform regular network and host vulnerability scans. These scans are conducted monthly to identify misconfigurations, exposed services, and known vulnerabilities across our infrastructure, including GCP-managed services and Kubernetes (GKE) nodes.

• Threat Intelligence & Monitoring:
  We rely on integrated security feeds and alerts from GCP SCC, Cloudflare, and Atatus to stay aware of vulnerabilities relevant to our environment. These tools provide continuous monitoring for new threat vectors and suspicious activity, especially at the network and application layers.

• Review & Mitigation:
  Identified vulnerabilities are triaged and reviewed by multiple team members, including engineers and release managers, to determine appropriate remediation. Patching decisions are prioritized based on severity, exploitability, and impact on production workloads.

• Tracking & Accountability:
  We maintain an internal tool, Db Dash, to track, manage, and resolve vulnerabilities. This ensures visibility into the status of each issue and accountability for timely remediation.

• Patch Management:
  While we do not currently use an automated patching system, all patches related to vulnerabilities identified through scans or alerts are manually assessed and applied as needed, with peer review and regression testing in our dedicated testing environment before production deployment.

This process ensures we proactively identify and manage risks in our cloud-hosted and containerized infrastructure, while also maintaining operational stability and compliance with basic security hygiene