Rec: 8.5.4 - Validate Test-DialInBypassLobby.ps1, ELevel: E3, ProfileLevel: L1, IG1: FALSE, IG2: FALSE, IG3: FALSE, Connection: Microsoft Teams

[DrIOSX]

Validation for Test-DialInBypassLobby.ps1

Recommendation Details

• Recommendation: 8.5.4
• Description: Ensure users dialing in can't bypass the lobby
• ELevel: E3
• Profile Level: L1
• CIS Control: 0
• CIS Description: Explicitly Not Mapped
• Implementation Group 1: FALSE
• Implementation Group 2: FALSE
• Implementation Group 3: FALSE
• Automated: TRUE
• Connection: Microsoft Teams

Test-DialInBypassLobby.ps1

Tasks

Validate recommendation details

• [x] Confirm that the recommendation details are accurate and complete as per the CIS benchmark.

Validate test for a pass

• [ ] Confirm that the automated test results align with the manual audit steps outlined in the CIS benchmark.
  • Specific conditions to check:
  • Condition A: The AllowPSTNUsersToBypassLobby setting in the Global Teams meeting policy is set to False.
  • Condition B: Verification using the UI in the Microsoft Teams admin center confirms that "People dialing in can't bypass the lobby" is set to Off.
  • Condition C: Ensure that individuals who dial in by phone must wait in the lobby until admitted by a meeting organizer, co-organizer, or presenter.

Validate test for a fail

• [ ] Confirm that the failure conditions in the automated test are consistent with the manual audit results.
  • Specific conditions to check:
  • Condition A: The AllowPSTNUsersToBypassLobby setting in the Global Teams meeting policy is not set to False.
  • Condition B: Verification using the UI in the Microsoft Teams admin center shows that "People dialing in can't bypass the lobby" is not set to Off.
  • Condition C: Individuals who dial in by phone are able to join the meeting directly without waiting in the lobby.

Add notes and observations

• [ ] Compare the automated audit results with the manual audit steps and provide detailed observations.
  • Automated audit produced info consistent with the manual audit test results? (Yes/No)
  • Without disclosing any sensitive information, document any discrepancies between the actual output and the expected output.
  • Document any error messages, removing any sensitive information before submitting.
  • Identify the specific function, line, or section of the script that failed, if known.
  • Provide any additional context or observations that might help in troubleshooting.

If needed, the helpers folder in .\source\helpers contains a CSV to assist with locating the test definition.

[DrIOSX]

Base PowerShell Audit:

Get-CsTeamsMeetingPolicy -Identity Global | fl AllowPSTNUsersToBypassLobby