@@ -5,16 +5,16 @@ revision-version: 1
|
||||
revision-date: "2024-01-07"
|
||||
estimate-time: "30m"
|
||||
frameworks:
|
||||
- name: "soc2"
|
||||
sections: ["CC6.1", "CC6.8"]
|
||||
- name: "soc2"
|
||||
sections: ["CC6.1", "CC6.8"]
|
||||
---
|
||||
|
||||
## Purpose
|
||||
SPF (Sender Policy Framework) prevents email spoofing by defining
|
||||
which mail servers are authorized to send emails on behalf of your
|
||||
domain. It helps receiving mail servers verify that incoming email
|
||||
from a domain comes from a host authorized by that domain's
|
||||
administrators.
|
||||
|
||||
SPF (Sender Policy Framework) prevents email spoofing by defining which mail
|
||||
servers are authorized to send emails on behalf of your domain. It helps
|
||||
receiving mail servers verify that incoming email from a domain comes from a
|
||||
host authorized by that domain's administrators.
|
||||
|
||||
## Implementation
|
||||
|
||||
@@ -35,10 +35,9 @@ administrators.
|
||||
- Create TXT record at domain root
|
||||
- Publish SPF record in DNS
|
||||
- Wait for DNS propagation
|
||||
|
||||
|
||||
## Evidence
|
||||
|
||||
- Screenshot of published SPF DNS record
|
||||
- Email header samples showing SPF pass
|
||||
- Documentation of authorized senders
|
||||
|
||||
|
||||
@@ -5,15 +5,16 @@ revision-version: 1
|
||||
revision-date: "2024-01-07"
|
||||
estimate-time: "30m"
|
||||
frameworks:
|
||||
- name: "soc2"
|
||||
sections: ["CC6.1", "CC6.8"]
|
||||
- name: "soc2"
|
||||
sections: ["CC6.1", "CC6.8"]
|
||||
---
|
||||
|
||||
## Purpose
|
||||
DKIM (DomainKeys Identified Mail) helps prevent email spoofing by
|
||||
adding a digital signature to outgoing messages, allowing receiving
|
||||
mail systems to verify that emails genuinely came from your domain and
|
||||
weren't modified in transit.
|
||||
|
||||
DKIM (DomainKeys Identified Mail) helps prevent email spoofing by adding a
|
||||
digital signature to outgoing messages, allowing receiving mail systems to
|
||||
verify that emails genuinely came from your domain and weren't modified in
|
||||
transit.
|
||||
|
||||
## Implementation
|
||||
|
||||
@@ -24,7 +25,8 @@ weren't modified in transit.
|
||||
3. Select your domain and click "Generate new record".
|
||||
4. Copy the DKIM TXT record provided by Google.
|
||||
5. Add this TXT record to your DNS.
|
||||
6. After DNS propagation, return to Admin console and click "Start authentication".
|
||||
6. After DNS propagation, return to Admin console and click "Start
|
||||
authentication".
|
||||
|
||||
## Evidence
|
||||
|
||||
|
||||
@@ -15,16 +15,18 @@ frameworks:
|
||||
---
|
||||
|
||||
## Purpose
|
||||
DMARC (Domain-based Message Authentication, Reporting, and
|
||||
Conformance) is a policy framework that builds upon SPF and DKIM. It
|
||||
tells receiving servers what to do when emails fail SPF or DKIM
|
||||
checks, and provides reporting on authentication results.
|
||||
|
||||
DMARC (Domain-based Message Authentication, Reporting, and Conformance) is a
|
||||
policy framework that builds upon SPF and DKIM. It tells receiving servers what
|
||||
to do when emails fail SPF or DKIM checks, and provides reporting on
|
||||
authentication results.
|
||||
|
||||
## Implementation
|
||||
|
||||
### Google Workspace
|
||||
|
||||
1. Create a Google Group named `dmarc-report@example.com` which is assecible from external users.
|
||||
1. Create a Google Group named `dmarc-report@example.com` which is assecible
|
||||
from external users.
|
||||
2. Create DMARC record in monitoring mode:
|
||||
```
|
||||
Record: _dmarc.example.com
|
||||
@@ -38,5 +40,6 @@ checks, and provides reporting on authentication results.
|
||||
authentication of emails.
|
||||
|
||||
## Evidence
|
||||
|
||||
- Screenshot of DMARC DNS record
|
||||
- Sample aggregate reports
|
||||
|
||||
@@ -5,16 +5,15 @@ revision-version: 1
|
||||
revision-date: "2024-01-07"
|
||||
estimate-time: "15m"
|
||||
frameworks:
|
||||
- name: "soc2"
|
||||
sections: ["CC6.8", "CC7.2"]
|
||||
- name: "soc2"
|
||||
sections: ["CC6.8", "CC7.2"]
|
||||
---
|
||||
|
||||
## Purpose
|
||||
|
||||
Implement email filtering and warning systems to reduce phishing risks
|
||||
and protect employees from malicious emails. This reduces mental load
|
||||
on employees and decreases company risk exposure through email-based
|
||||
attacks.
|
||||
Implement email filtering and warning systems to reduce phishing risks and
|
||||
protect employees from malicious emails. This reduces mental load on employees
|
||||
and decreases company risk exposure through email-based attacks.
|
||||
|
||||
## Implementation
|
||||
|
||||
@@ -27,13 +26,13 @@ attacks.
|
||||
```
|
||||
3. Configure "Safety" settings:
|
||||
- Attachments Protection
|
||||
- Scan for anomalous attachment types
|
||||
- Block attachments with scripts
|
||||
- Block encrypted attachments from untrusted senders
|
||||
- Scan for anomalous attachment types
|
||||
- Block attachments with scripts
|
||||
- Block encrypted attachments from untrusted senders
|
||||
- Links and External Images:
|
||||
- Enable scanning of linked images
|
||||
- Identify shortened URLs
|
||||
- Display warning prompts for untrusted domains
|
||||
- Enable scanning of linked images
|
||||
- Identify shortened URLs
|
||||
- Display warning prompts for untrusted domains
|
||||
|
||||
## Evidence
|
||||
|
||||
|
||||
Reference in New Issue
Block a user