Security Proposal Workspace / Project 004

Practice Labs

Follow two findings through the assessment, then practice collecting the kind of evidence a reviewer would ask for. Use fictional data and dedicated test accounts for all exercises.

REQ-007 / PR.AA-03

MFA Coverage Verification

The fictional advertising account control is marked implemented. Follow the requirement to CTL-007, then see what changes when you link the reviewed record EV-007.

Open the MFA reassessment · Read the fictional evidence record

In the browser workspace, select Open full sample in editor, then Edit MFA control and link EV-007. Return to the comparison and review again to see what changed.

Try it in a test tenant

Run the Conditional Access What If exercise with a test identity and an application in scope. Compare a case that matches the policy with an excluded or out-of-scope case. What If simulates policy evaluation. An observed test sign-in and its Authentication Details provide separate evidence of the sign-in outcome.

Microsoft Learn Conditional Access exercise · Microsoft Entra MFA reporting guidance

Record for review

  • The test application, identity or group, policy scope, and any exceptions.
  • The expected outcome, simulated result, and date. If you also performed a test sign-in, record its observed outcome separately.
  • The control owner, reviewer decision, and any remaining gaps. A sample sign-in covers the tested conditions. Verify account coverage separately.

REQ-010 / PR.DS-11

Backup Restoration Testing

Follow ACT-008 to the campaign-file backup finding. Compare the original partial implementation, an action marked ready for review, and the fictional reassessment after work and review are recorded.

Open the backup reassessment · Read the fictional restore evidence

In the browser workspace, open the full sample in the editor and change only CTL-010 to implemented. Review again. The incomplete restore notes keep the finding open. Record the simulated completed restore and update its evidence to finish the exercise.

Restore a sample file locally

From the Security Proposal Workspace source folder, run the helper with a new output folder. It checks each backup copy against the saved SHA-256 hash before restoring and then checks the restored file. Read restore-results.json to see the successful restore and the rejection of a changed copy. This exercise needs Python and works without a cloud account.

python -B practice_restore.py --output my-restore-practice

For an optional cloud exercise, use an Azure lab environment with a test virtual machine protected by Azure Backup. Choose a recovery point and recover a sample file to a separate location. Microsoft Learn Azure file restore tutorial

Record for review

  • The sample file and backup copy, restore destination, result, and run date. For a cloud restore, include the selected recovery point and job result.
  • The original, backup, and restored SHA-256 hashes. Record whether each backup was accepted and whether a restore destination was created.
  • The backup scope and protection settings that still need review. The local file restore illustrates REQ-010. Rejecting the changed copy before restoring illustrates the separate integrity check in REQ-015.

Governance practice

After Task 4 of the TryHackMe room, pick a fictional asset and write down one risk, the mapped control, who owns it, what evidence supports it, and what still needs a decision. Use a finding from the Dossier to ground the exercise. TryHackMe Cyber Governance and Regulation

Read the source walkthrough and run commands