TECHNOLOGY · PRACTICE · EVIDENCE

Skills backed by practice

My focus is Microsoft security engineering. This page separates demonstrated activity from areas I am still developing.

Experience should be verifiable.

These are the tools and disciplines I work with or am learning. A technology listed here is not automatically proof of proficiency. Follow the linked cases to see the recorded checks and limitations.

01

Microsoft Intune & Autopilot

Hands-on, ongoing

Device enrollment, user-driven Windows Autopilot and MDM management.

Evidence boundary

User observed device management by Microsoft Intune; effective policy and ESP outcomes still pending.

View enrollment evidence
02

Microsoft Entra ID

Hands-on, ongoing

Cloud device identity, sign-in and PRT validation in an authorized test environment.

Evidence boundary

AzureAdJoined = YES and AzureAdPrt = YES, user-observed on 3 November 2026.

View device trust checks
03

OSINT & investigative thinking

Guided case completed

Metadata inspection, corroboration of public clues and risk assessment.

Evidence boundary

7/7 OhSINT questions with coaching; precise limits of independent verification recorded.

View investigation
04

Microsoft Defender

Learning focus

Endpoint security controls, monitoring and investigation workflows.

Evidence boundary

Not yet presented as a completed validated Defender case.

Browse projects
05

Microsoft Sentinel & KQL

Planned

Detection engineering, query validation and monitoring scenarios.

Evidence boundary

Practical detection implementation has not yet been demonstrated.

View planned track
06

Security automation

Planned

PowerShell, Microsoft Graph and repeatable reporting with least privilege.

Evidence boundary

No independently verified automation project published yet.

View current work

Why evidence matters

My documentation distinguishes a configured control from a tested outcome. I record remaining gaps rather than declaring a project complete too early.

Explore the case studies