Phase 2 · Security Operations Expansion

Endpoint, Identity
& Compliance Ops

A Microsoft 365 enterprise security expansion covering Intune endpoint governance, Entra ID identity hardening, Purview compliance controls, Conditional Access, RBAC, DLP, and Exchange Online mail security — all deployed in safe, governance-first modes across 4 admin centers.

Security Architecture

Six Control Areas

Phase 2 expands the Meridian lab into a multi-admin-center security operations environment — hardening identity, governing endpoints, protecting sensitive data, and securing mail flow.

🖥️

Endpoint Governance

  • Windows compliance policy — OS, password, firewall
  • Defender antivirus & BitLocker enforcement
  • Endpoint security baseline (Microsoft recommended)
  • Update ring & deployment ring configuration
  • PowerShell validation commands for endpoint reporting
🔐

Identity & Access (RBAC)

  • Helpdesk-Level1 delegated admin role assignment
  • Security Reader role for SOC personnel
  • MFA-required security group design
  • Least-privilege scoping per persona
  • SSPR configuration & authentication methods
🛡️

Conditional Access

  • Report-only MFA enforcement for admin roles
  • Legacy authentication block policy
  • Compliant-device access control (report-only)
  • Staged rollout — zero user disruption
  • CA policy visibility & audit evidence
📋

Microsoft Purview

  • DLP policies for Canadian sensitive data types (SIN, health cards)
  • Communication Compliance policy creation
  • Retention label workflow (Exchange + SharePoint)
  • Compliance Manager & NIST SP 800-53 assessment
  • Sensitivity labeling & information protection
📬

Exchange Online

  • IT Helpdesk shared mailbox provisioned
  • Mailbox address & display name configured
  • Transport rule — block external auto-forwarding
  • Anti-spam, anti-malware, Safe Attachments
  • DKIM signing & mail flow governance

Security Operations Narrative

  • Least-privilege administration throughout
  • Data exfiltration risk reduction (DLP + transport)
  • Governance-first policy design (report-only default)
  • Operational documentation & evidence capture
  • Cross-admin-center security posture alignment
Operational Sequence

Build Order

Each control area built sequentially — later steps assumed earlier ones were in place.

1 — Endpoint Governance Baseline

Documented and configured Intune compliance controls: Windows security baseline, update rings, Defender and firewall policies, BitLocker enforcement, and PowerShell validation commands for endpoint state reporting.

2 — Purview Compliance Expansion

Created DLP policies targeting Canadian PII (SIN, health card numbers), Communication Compliance policies, retention labels for Exchange and SharePoint, and captured Compliance Manager / NIST assessment evidence.

3 — Entra ID & Conditional Access Hardening

Built RBAC delegated admin roles (Helpdesk, Security Reader), MFA security groups, SSPR configuration, and Conditional Access report-only policies for MFA enforcement, legacy auth blocking, and compliant-device access.

4 — Exchange Online Mail Security

Provisioned the IT Helpdesk shared mailbox, configured address and display name, created a transport rule to block external auto-forwarding, and reviewed anti-spam, Safe Attachments, and DKIM governance.

Validation Layer

PowerShell as the Control Validator

PowerShell commands were used to validate endpoint compliance states, Exchange mail flow rules, Purview policy deployment, and Entra ID role/CA configurations — making every control evidence-backed and repeatable.

01 · Intune Validation
02 · Exchange Online
03 · Purview & DLP
04 · Entra ID & CA
PowerShell — Intune Endpoint Compliance Validation
# Connect to Microsoft Graph with Intune scopes
Connect-MgGraph -Scopes "DeviceManagementConfiguration.Read.All","DeviceManagementManagedDevices.Read.All"

# List all device compliance policies
Get-MgDeviceManagementDeviceCompliancePolicy | Select DisplayName,Id,CreatedDateTime

# List compliance policy assignments
Get-MgDeviceManagementDeviceCompliancePolicy -All |
  ForEach-Object {
    $policy = $_
    Get-MgDeviceManagementDeviceCompliancePolicyAssignment -DeviceCompliancePolicyId $policy.Id |
      Select @{N='Policy';E={$policy.DisplayName}}, Target
  }

# List endpoint security baselines
Get-MgDeviceManagementIntent | Select DisplayName,TemplateName,IsAssigned

# Validate device configuration profiles
Get-MgDeviceManagementDeviceConfiguration | Select DisplayName,OdataType,LastModifiedDateTime
PowerShell — Exchange Online Mail Flow Validation
# Connect to Exchange Online
Connect-ExchangeOnline

# Validate shared mailbox creation
Get-Mailbox -RecipientTypeDetails SharedMailbox | Select DisplayName,PrimarySmtpAddress,Alias

# List all transport / mail flow rules
Get-TransportRule | Select Name,State,Priority,Description

# Validate external auto-forwarding block rule
Get-TransportRule | Where-Object { $_.Name -like "*forward*" } |
  Select Name,State,RedirectMessageTo,RejectMessageEnhancedStatusCode

# Check remote domain forwarding settings
Get-RemoteDomain | Select DomainName,AutoForwardEnabled,AllowedOOFType

# Verify anti-spam / connection filter policies
Get-HostedConnectionFilterPolicy | Select Name,IsDefault,IPAllowList,IPBlockList
PowerShell — Purview Compliance & DLP Validation
# Connect to Security & Compliance PowerShell
Connect-IPPSSession

# List all DLP policies and their state
Get-DlpCompliancePolicy | Select Name,Mode,Workload,CreatedBy,WhenCreated

# List DLP rules under each policy
Get-DlpComplianceRule | Select Name,ParentPolicyName,BlockAccess,NotifyUser

# Validate retention labels
Get-ComplianceTag | Select Name,RetentionDuration,RetentionAction,IsRecordLabel

# List retention policies and their locations
Get-RetentionCompliancePolicy | Select Name,Enabled,ExchangeLocation,SharePointLocation

# Check communication compliance policies
Get-SupervisoryReviewPolicy | Select Name,Enabled,Reviewers,SamplingRate

# Result: DLP policies — Canadian PII types protected
# SIN (Canada Social Insurance Number), Health Card — active in Exchange+SharePoint+Teams
PowerShell — Entra ID RBAC & Conditional Access Validation
# Connect with identity + CA read scopes
Connect-MgGraph -Scopes "RoleManagement.Read.Directory","Policy.Read.All"

# List all active role assignments in the tenant
Get-MgRoleManagementDirectoryRoleAssignment -All |
  Select RoleDefinitionId,PrincipalId,DirectoryScopeId

# Show role display names + assigned users
Get-MgDirectoryRole | ForEach-Object {
  $role = $_
  Get-MgDirectoryRoleMember -DirectoryRoleId $role.Id |
    Select @{N='Role';E={$role.DisplayName}}, @{N='Member';E={$_.Id}}
}

# List all Conditional Access policies + their state
Get-MgConditionalAccessPolicy | Select DisplayName,State,CreatedDateTime

# Result: 3 CA policies — all in Report-Only (safe staged mode)
# Require MFA for Admin Roles       → reportOnly
# Block Legacy Authentication        → reportOnly
# Require Compliant Device           → reportOnly
Control Evidence

116 Evidence Screenshots

Configuration evidence across Microsoft Intune, Entra ID, Purview, Exchange Online, and PowerShell — cleaned, organized, and documented for portfolio walkthroughs and interview storytelling.

Portfolio Value

Skills & Impact Demonstrated

Phase 2 proves hands-on security administration across identity, compliance, endpoint, and email governance — not just basic tenant configuration.

🔐 Security Administration

  • Conditional Access policy design and staging in report-only mode
  • RBAC least-privilege scoping — Helpdesk, Security Reader, Global Admin
  • MFA enforcement strategy with security group targeting
  • Legacy authentication elimination via transport-level block
  • Zero Trust posture implementation across 4 admin centers

📋 Compliance & Data Governance

  • DLP policies scoped to Canadian PII (SIN, provincial health card)
  • Retention label lifecycle — creation, policy, deployment
  • Communication Compliance for regulatory monitoring
  • Compliance Manager + NIST SP 800-53 assessment evidence
  • Sensitivity labeling and information protection workflow

🖥️ Endpoint & Device Management

  • Windows compliance policy — OS, Defender, BitLocker, firewall, password
  • Microsoft Security Baseline applied via Endpoint Security
  • Update ring configuration with staged deployment strategy
  • PowerShell Graph API validation of all endpoint controls
  • Intune settings catalog — granular Windows security rules

📬 Mail Security & Operations

  • Shared mailbox provisioning with delegated access control
  • Transport rule — auto-forwarding exfiltration protection
  • Anti-spam and anti-malware policy validation
  • Safe Attachments and Safe Links — Defender for Office 365
  • DKIM signing and remote domain governance
Portfolio positioning:

This phase demonstrates that Meridian Institute is more than a tenant setup — it's a simulated enterprise security operations environment covering identity hardening, compliance governance, endpoint management, and mail flow security. Each control area is evidence-backed and interview-ready.