P

Power Gws Alertcenter

Comprehensive command designed for google, workspace, alert, center. Includes structured workflows, validation checks, and reusable patterns for google workspace.

CommandClipticsgoogle workspacev1.0.0MIT
0 views0 copies

Power GWS Alertcenter

Execute Google Workspace Alert Center operations to manage security alerts, threat notifications, and incident response.

When to Use This Command

Run this command when you need to:

  • Monitor and triage security alerts for phishing, malware, or suspicious login activity across your domain
  • Acknowledge, investigate, or close Alert Center incidents programmatically
  • Generate security status reports summarizing active threats and resolution timelines

Consider alternatives when:

  • You need historical audit data older than the Alert Center retention period, use Admin Reports instead
  • You want to set up proactive rules and policies rather than respond to existing alerts

Quick Start

Configuration

name: power-gws-alertcenter type: command category: google-workspace

Example Invocation

claude command:run power-gws-alertcenter --action list --status active --severity high

Example Output

Fetching Alert Center alerts...
  Filter: status=active, severity=high
  Domain: example.com

Active High-Severity Alerts: 3

1. [PHISHING] Suspected phishing campaign targeting finance team
   Created: 2026-03-14 09:22 UTC
   Affected users: 12
   Status: ACTIVE

2. [SUSPICIOUS_LOGIN] Multiple failed logins from unusual location
   Created: 2026-03-14 14:05 UTC
   Affected users: 1
   Status: ACTIVE

3. [DATA_EXPORT] Large Drive data export detected
   Created: 2026-03-15 02:11 UTC
   Affected users: 1
   Status: ACTIVE

Actions available: acknowledge, investigate, close

Core Concepts

Alert Center Overview

AspectDetails
Alert TypesPhishing, malware, suspicious login, data export, device compromise, DLP
Severity LevelsLow, medium, high, critical with automatic escalation rules
LifecycleActive -> Acknowledged -> Investigating -> Closed with full audit trail
IntegrationFeeds into SIEM systems, Slack notifications, and incident response tools
RetentionAlerts retained for 180 days with full metadata and affected user lists

Alert Triage Workflow

New Alert Created
       |
       v
Severity Assessment
  |         |        |
  v         v        v
 Low     Medium    High/Critical
  |         |        |
  v         v        v
 Queue   Review    Immediate
  |         |      Response
  v         v        |
Acknowledge       Investigate
       |              |
       v              v
    Resolve        Remediate
       |              |
       v              v
      Close         Close

Configuration

ParameterTypeDefaultDescription
actionstringlistAction to perform: list, acknowledge, investigate, close
statusstringactiveFilter by alert status: active, acknowledged, closed
severitystringallFilter by severity: low, medium, high, critical
alert-idstring(none)Specific alert ID for acknowledge, investigate, or close
daysinteger7Number of days of alert history to retrieve

Best Practices

  1. Triage by severity immediately - High and critical alerts should be reviewed within minutes. Set up the command as a scheduled check or integrate with your on-call notification system.

  2. Document investigation steps - When transitioning an alert to investigating status, add notes about what you found. This creates an audit trail that compliance teams require.

  3. Correlate with Admin Reports - An alert about suspicious login activity becomes actionable when combined with the full login report for that user. Pull both data sources during investigation.

  4. Close resolved alerts promptly - Stale active alerts create noise and make it harder to spot new genuine threats. Close alerts once remediation is confirmed complete.

Common Issues

  1. No alerts returned despite known issues - Verify your account has Alert Center admin privileges. Standard user accounts cannot access domain-wide security alerts.

  2. Alert status update fails - Some alerts require specific admin roles to modify. Check that your service account has the alertcenter.alerts.update permission.

  3. Duplicate alerts for the same incident - Google may create separate alerts for related events. Use the alert metadata to identify and group related alerts during triage.

Community

Reviews

Write a review

No reviews yet. Be the first to review this template!

Similar Templates