用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/CyberStrikeus/CyberStrike --skill cis-gworkspace-3-1-3-2-3命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
macOS post-exploitation for credential harvesting, DTrace monitoring, TCC bypass, and stealth operations via native tools
Windows userland post-exploitation for credential harvesting, monitoring, AMSI/ETW bypass, and stealth operations
Kubernetes post-exploitation for container escape, secret extraction, RBAC abuse, and cluster persistence
正在显示 SKILL.md
基于 SOC 职业分类
| name | cis-gworkspace-3.1.3.2.3 |
| description | Ensure the DMARC record is configured for all mail enabled domains |
| category | cis-gworkspace |
| version | 1.3.0 |
| author | cyberstrike-official |
| tags | ["cis","gcp","google-workspace","gmail","dmarc","email-security"] |
| cis_id | 3.1.3.2.3 |
| cis_benchmark | CIS Google Workspace Foundations Benchmark v1.3.0 |
| tech_stack | ["gcp","google-workspace"] |
| cwe_ids | [] |
| chains_with | ["cis-gworkspace-3.1.3.2.1","cis-gworkspace-3.1.3.2.2"] |
| prerequisites | [] |
| severity_boost | {} |
| Property | Value |
|---|---|
| CIS ID | 3.1.3.2.3 |
| Level | L1 |
| Profile Applicability | Enterprise Level 1 |
| Assessment Type | Manual |
| Section | Gmail > Authenticate email |
For all email domains configured in Google Workspace, a corresponding Domain-Based Message Authentication, Reporting and Conformance (DMARC) record should be created.
NOTE: There are a number of ways DMARC can be configured, this document presents a most basic method. For more information on setting up DMARC for Google Workspace please refer to the Google documentation.
DMARC works with Sender Policy Framework (SPF) and Domain Keys Identified Mail (DKIM) to authenticate mail senders and ensure that destination email systems trust messages sent from your domain. Spammers can spoof your domain or organization to send fake messages that impersonate your organization. DMARC tells receiving mail servers what to do when they get a message that appears to be from your organization, but doesn't pass authentication checks, or doesn't meet the authentication requirements in your DMARC policy record. Messages that aren't authenticated might be impersonating your organization, or might be sent from unauthorized servers.
There should be minimal impact of setting up DMARC records however, organizations should ensure proper DMARC record setup as email could be flagged as spam if DMARC is not set up appropriately.
None
Check the DNS records for each domain.
nslookup tool on your workstation OSv=DMARC1; p=none; rua=mailto:<report@domain1.com> exists. This designates Google Gmail as an authorized sender.NOTE: The p=none sets DMARC to non-enforcing. This is a relaxed DMARC policy that lets you start getting reports without risking messages from your domain being rejected or marked as spam by receiving servers. Start with a none policy that only monitors email flow, and then eventually change to a policy that rejects all unauthenticated messages (p=reject).
NOTE: The rua=mailto: entry is optional but setting it to a valid email address is recommended. RUA reports provide a comprehensive view of all of a domain's traffic. At a minimum, organizations should configure their DMARC record to receive RUA reports.
Configure the DNS record for each domain.
v=DMARC1; p=none; rua=mailto:<report@domain1.com>
NOTE: This will likely need to be configured at your domain registrar (Godaddy, etc.).
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
|---|---|---|---|---|
| v8 | 9.5 Implement DMARC | x | x | |
| v7 | 7.8 Implement DMARC and Enable Receiver-Side Verification | x | x |