generated from cisagov/ScubaGear
-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gmail Clarify Bypassing Spam Filters #149
Comments
@adhilto We will implement the recommended changes. |
14 tasks
PR has been created. TTP Mappings still need to be done and drift rules need to be created. |
Drift Rules have been completed. Now only waiting on TTP mappings. |
Followed-up on the status of the TTP mappings. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
(Using the numbers of the gmail-changes-1 branch)
GWS.GMAIL.14.1v0.1 instructs users to not use an email allowlist, referring to this feature here:
![image](https://private-user-images.githubusercontent.com/106177711/296893724-19fd42d0-a6de-4960-a415-e65d1996a548.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk4MTcyNTMsIm5iZiI6MTczOTgxNjk1MywicGF0aCI6Ii8xMDYxNzc3MTEvMjk2ODkzNzI0LTE5ZmQ0MmQwLWE2ZGUtNDk2MC1hNDE1LWU2NWQxOTk2YTU0OC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjE3JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIxN1QxODI5MTNaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0wODc0ZDVmNGFhODNjN2EyNjFlMzczYWYyOGFmMzA2NjlkYzdmOGJhNTc4ZGE1MzFmZThiMzQ0MDEyY2RjYjgwJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.xUP-g6O8FKNe0IHraOtesRMiVaWphRZjk3bkhWmNGA4)
However, there is another way to create an allowlist that the baseline does not address:
![image](https://private-user-images.githubusercontent.com/106177711/296894112-8e27e27e-f7dc-4bff-8e91-7d05baab6dd4.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk4MTcyNTMsIm5iZiI6MTczOTgxNjk1MywicGF0aCI6Ii8xMDYxNzc3MTEvMjk2ODk0MTEyLThlMjdlMjdlLWY3ZGMtNGJmZi04ZTkxLTdkMDViYWFiNmRkNC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjE3JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIxN1QxODI5MTNaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT01NmVjNWU1OGM0ZDVjNjBiYTNmZGQzYTM4M2IyOTJiMzdhZWM5MTk5NTQ1ZDE4MzY0MTA3NjE3NjI4MDkyOTA0JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.2SvttRzGW88TL1SkAt8S2xEgxsgdl6EH1fEzvXDjbJk)
What was previously GWS.GMAIL.18 touched on some of these settings, but this group is being deleted. I agree with the deletion of this group--the guidance there was confusing and contradictory--but I would recommend adding a new control group that rules out the various ways users could bypass spam protections.
Proposed group name: "Spam Filtering"
Policies:
The text was updated successfully, but these errors were encountered: