Security Command Center¶
When the SCC data source is enabled, the results analyzed by the Google Cloud Security Command Center (SCC) service are collected.
What is Security Command Center?
- SCC is a security service for threat detection provided by Google.
- To see what items are detected by SCC, please refer to the official documentation .
Security Command Center is a solution for organizations
SCC is a security service for organizations .
- To enable the settings, you must belong to some organization.
- Service accounts must also be registered with the organization's IAM.- Set the following roles for the service account:- Security Center Findings Viewer (roles/securitycenter.findingsViewer)
 
- Security Center Findings Viewer (
- Alternatively, set a custom role that includes the following permissions (SCC reference permissions):
- securitycenter.findings.group - securitycenter.findings.list - securitycenter.findings.listFindingPropertyNames - securitycenter.sources.get - securitycenter.sources.list
- For more information, see Granting service account permissions.
 
- Set the following roles for the service account:
Format¶
When importing data into RISKEN, the following metadata is added:
| Field Name | Description | 
|---|---|
| DataSource | google:scc (fixed value) | 
| ResourceName | Name of the detected asset | 
| Description | Description | 
| Score | Refer to Scoring | 
| Tag | googlegcpscc{project ID}{service name} | 
Scoring¶
The result data analyzed by Security Command Center has Severity information .
When importing into RISKEN, scoring is performed based on the Severity using the following logic.
graph TD
    A[Start] --> B{{Status Active?}};
    B -->|NO| C[Score: 0.1]:::low;
    B -->|YES| D{{Severity = LOW?}};
    D -->|YES| E[Score: 0.1]:::low;
    D -->|NO| F{{Severity = MEDIUM?}};
    F -->|YES| G[Score: 0.3]:::low;
    F -->|NO| H{{Severity = HIGH?}};
    H -->|YES| I[Score: 0.6]:::mid;
    H -->|NO| J{{Severity = CRITICAL?}};
    J -->|YES| K[Score: 0.9]:::high;
    J -->|NO| L[Score: 0.0]:::unknown;
    classDef high fill:#FFFFFF,stroke:#C2185B,stroke-width:4px;
    classDef mid fill:#FFFFFF,stroke:#F57C00,stroke-width:4px;
    classDef low fill:#FFFFFF,stroke:#4DB6AC,stroke-width:4px;
    classDef unknown fill:#FFFFFF,stroke:#BDBDBD,stroke-width:4px;
About Triage¶
Scores calculated by the data source may be re-evaluated by RISKEN's Auto-Triage feature.
Findings with CVE-ID¶
In addition to CVSS scores, findings are re-evaluated based on whether a PoC has been published or whether there is a history of actual exploitation.
For Enterprise or Premium Tier¶
System exposure and business impact are calculated based on Attack exposure scores .
- Findings are triaged from a system exposure perspective based on the Attack Exposurescore
- Findings are triaged from a business impact perspective based on the presence of High/Medium Resources