Cloud SIEM: GCP + Chronicle Security Operations

The Problem and Why It Mattered

I designed and deployed a cloud-native SIEM environment using Google Chronicle — complete log ingestion pipeline, 14 custom YARA-L detection rules, automated incident triage, and a documented incident response playbook. The relevant technical and business risk is the cost of leaving this workflow, control, or product boundary unclear, manual, insecure, or difficult to operate. The case study focuses on the decisions used to make that risk manageable.

Objectives and Success Criteria

• Deliver the capability described in the project objective using a maintainable technical design.
• Make the main workflow, control boundary, and operational responsibilities explicit.
• Produce reviewable implementation evidence without publishing confidential values or customer data.

Requirements and Constraints

The security design had to improve control coverage without exposing sensitive architecture, credentials, customer data, or internal findings in the public record.

My Role and Ownership

I owned the technical design and implementation described in this portfolio record, including the technology choices, core system boundaries, and the documentation of the resulting approach. Related organisational decisions, vendor operations, and formal certification decisions remain outside the scope of this technical case study unless stated explicitly.

Solution Overview

The solution is built around Chronicle SIEM, YARA-L, Cloud Functions. Its implementation is organised as the components below so that the architecture, control points, and operating model can be evaluated separately rather than treated as a list of tools.

Architecture and System Design

The public architecture description follows the path from the initiating user, workload, or operator action through the relevant cybersecurity components. Access boundaries, data or state handling, and operational controls are described at a safe level; secrets, private addresses, and client-sensitive implementation details are intentionally omitted.

Technology Decisions and Trade-Offs

I selected Chronicle SIEM, YARA-L, Cloud Functions because they support the project objective and make the critical engineering boundaries explicit. The trade-off is operational and platform complexity: the design depends on documented configuration, controlled access, and ongoing review rather than assuming that a managed service or framework removes engineering responsibility.

Implementation Walkthrough

The following implementation notes describe the components that matter most to the project outcome. They are intentionally focused on technical decisions and operating behaviour instead of reproducing entire source files or sensitive configuration.

Implementation: Log Ingestion Architecture

I built a centralised log ingestion pipeline collecting from Cloud Audit Logs, VPC Flow Logs, Cloud Armor request logs, GKE audit logs, Cloud Run access logs, and Firebase Authentication events. Logs flow through Cloud Logging → Pub/Sub → Chronicle ingestion API via a Cloud Functions forwarder.

Implementation: Detection Engineering — 14 Custom YARA-L Rules

Rules covering: service account key creation outside approved CI pipelines; privilege escalation via IAM policy binding changes; impossible travel authentication events; Cloud Storage exfiltration (high-volume GetObject calls); container escape indicators in GKE audit logs; brute force against Cloud IAP-protected services.

Implementation: Alert Triage & Enrichment

Alerts trigger a Cloud Functions enrichment step that pulls WHOIS and GeoIP data for external IPs, IAM policy history for the involved principal, and recent Cloud Audit Log activity. Enriched alerts route to PagerDuty with severity-appropriate escalation.

Implementation: Incident Response Playbook

I documented a full IR playbook for five scenarios: compromised service account key, unauthorised IAM escalation, Cloud Storage data exfiltration, cryptomining workload in GKE, and Cloud Armor bypass attempts.

Implementation: BigQuery Threat Hunting

Chronicle detections and raw UDM events export to BigQuery for long-term threat hunting. Scheduled BigQuery queries run weekly to surface slow-burn threats — gradual permission creep, low-and-slow data staging.

Implementation: Results

Mean time to detection (MTTD): 4.2 minutes. Mean time to containment (MTTC): 18 minutes with automated enrichment. Zero false-positive P1 alerts in 90 days of operation.

Challenges, Failures and Corrections

This portfolio record does not invent deployment failures, client incidents, or corrective actions that are not supported by the published project evidence. Where operational details are confidential or were not captured for public release, the case study documents the design boundary and lesson instead of presenting an unsupported narrative.

Security, Compliance and Risk

The implementation is described with least privilege, traceability, controlled configuration, and evidence boundaries in mind. Where the project supports a regulated environment, these are technical safeguards and audit-readiness contributions, not a claim that an application or product is independently certified.

Testing, Validation and Evidence

The evidence published for this project is the documented implementation, its stated architecture and controls, and the portfolio record. Mean time to detection (MTTD): 4.2 minutes. Mean time to containment (MTTC): 18 minutes with automated enrichment. Zero false-positive P1 alerts in 90 days of operation. Claims are limited to the implementation details and outcomes documented in this case study.

Results and Evidence

Mean time to detection (MTTD): 4.2 minutes. Mean time to containment (MTTC): 18 minutes with automated enrichment. Zero false-positive P1 alerts in 90 days of operation.

What I Learned

This project reinforced that cybersecurity work is not a technology checklist. The durable value comes from making boundaries, trade-offs, ownership, and evidence clear enough for another engineer or stakeholder to review and operate the system responsibly.

What I Would Improve Next

• Expand automated validation around the most important workflow and control boundaries.
• Add or deepen operational evidence, such as dashboards, test artefacts, or an architecture diagram where it is safe to publish one.
• Review the design against the next expected scale, reliability, and governance requirement before extending the system.

Final Takeaway

This cloud security engineering case study addresses a defined technical problem through Chronicle SIEM, YARA-L, Cloud Functions. It demonstrates my ability to turn requirements into an explainable design, implement the important controls, and document outcomes and limitations without overstating what the evidence proves.