Identity and access
In progressEntra ID, RBAC, least privilege, and AZ-104 identity objectives are active study areas.
Security
Defender-style previewA mock Microsoft Defender / Azure security blade for the portfolio itself: what is protected, what is planned, and what the project proves.
78 /100
Mock score. The point is the story: privacy-by-default content sync now, backend guardrails before AI goes live.
Data protection
ConfiguredPublic-safe content allowlist, phone-number scrub requirement, and explicit vault denylist.
Application security
PlannedPhase 3 keeps Azure OpenAI secrets server-side in Azure Functions, then moves toward managed identity.
Monitoring
PlannedFuture Cloudflare Web Analytics or Azure-native telemetry with no invasive tracking.
Recommendations
- Add managed identity for Azure Functions to call Azure OpenAI without API keys.
- Add rate limiting before enabling natural-language chatbot requests.
- Add robots.txt and confirm private paths never ship in dist.
- Keep the phone-number privacy grep clean before every deploy.