Remove Meet policy 5.1

[snarve]

Prerequisites

• This issue has an informative and human-readable title.

ScubaGoggles Version

v0.7

Operating System

N/A

Python Version

N/A

🐛 Summary

While going through log based SHALL policies noticed that Meet policy 5.1 is dependent on another advanced multiple regions policy

Steps to reproduce

1. In the Google admin console
2. Go to Apps -> Google Meet -> Meet Safety Settings -> Incoming call restrictions
3. There is warning there that this setting is applicable when the advanced data regions settings is enabled
4. Refer to the screen shot
5. As shown in the screen capture, the Meet setting is disabled, because the the advanced region setting is currently disabled and preferred to keep it as disabled to prevent data sharing across multiple regions

Question: Does this need to be noted in the implementation steps in the baseline doc?

Note: Currently the advanced data regions settings is disabled, however as stated in the note this setting should be enabled for the Incoming call restrictions setting to take effect.

The Advanced Setting can be manged at a application level.

[jkaufman-mitre]

Here is the dependent setting

[snarve]

Update from Mary and discussion with the team:

This does not seem to be a security issue since calls can be ignored if a user does not want to accept the call. Consensus was to remove this policy.

[FollyBeachGurl]

@snarve please refine this issue to delete policy 5.1.

[snarve]

Based on response from Mary and group discussion this policy can be removed.

[snarve]

@FollyBeachGurl updated the issue, its ready now

[jkaufman-mitre]

@snarve I am going to assign these changes to the TCO for this baseline.

[snarve]

@snarve I am going to assign these changes to the TCO for this baseline.

Can address the code and baseline update in the same PR/branch