Google Security Operations

Google Security Operations for your CMMC logs and alerts.

Log collection and alerting for a Google Workspace CUI enclave, configured for you and scoped around who will act on what it finds.

What it is

Google Security Operations, formerly known as Chronicle, is Google's cloud-native security operations platform. Google describes it as helping security teams detect, investigate and respond to threats, with SIEM, SOAR and threat intelligence in one product.

It is a Google product, licensed from Google. Our part is the setup described below.

What we set up

We configure Google Security Operations to take in your enclave tenant's logs and to raise alerts on them. Google documents ingestion of Google Workspace logs, including activity events and alerts.

The service is offered with our Google Workspace CUI enclave. If you want other log sources included, we discuss them during scoping. Google's product page states that its packages include one year of security telemetry retention.

The logs and alerts we work with are security data. We never handle CUI.

Licenses and price: Google Security Operations licenses are arranged by quote. Contact sales.

CMMCSync is built by HanumanLabs, a Google Cloud partner.

Who watches the alerts

An alert helps only when someone reviews it and acts. Who does that for you, and how, is a decision we settle together during scoping, before any setup begins.

How it relates to CMMC Level 2

Level 2 is assessed against the 110 requirements of NIST SP 800-171 Rev 2. Log collection and alerting relate to three of its requirement families.

Audit and Accountability (3.3)

3.3.1: “Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity.”

Collected and retained enclave logs help you produce evidence for this family.

Incident Response (3.6)

3.6.1: “Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, and user response activities.”

Alerts support the detection and analysis steps. The rest of the capability is people and process that you put in place.

System and Information Integrity (3.14)

3.14.6: “Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks.” 3.14.7: “Identify unauthorized use of organizational systems.”

Alert rules on the enclave’s activity support these requirements, together with the review your team does.

Requirement text: NIST SP 800-171 Rev 2.

What it is not

  • Not a monitoring service. We set up the collection and the alerts. Reviewing and responding to them is the role agreed during scoping.
  • Not a certification. Logs and alerts support parts of Level 2; they do not decide it. That is what your assessment is for.

Want logs and alerts for your enclave?

Tell us which systems you want covered and who on your side handles security today.

Talk to us