More often than not, today’s engineering happens inside AI-assisted development environments (IDE's). While this boosts productivity, it also introduces a new risk: secrets leaking into prompts, suggestions, logs, or chat history. This session shows how to set up a local engineering environment using PowerShell so secrets never end up in code, source control, or an IDE’s AI assistant.

The session starts with pragmatic local engineering patterns: separating configuration from code, structuring local secret files, and using .gitignore correctly to prevent accidental exposure. From there, it moves to a secure-by-default approach using the PowerShell SecretManagement and SecretStore modules. Encrypted vault registration, safe unlocking, and runtime secret consumption are covered without leaking sensitive values into scripts, terminals, AI prompts or sharing them with AI Assistants lurking in your development environment.

As a demo, secure authentication to Azure and Azure DevOps is demonstrated using PowerShell without exposing credentials to environment variables, clipboard history, or AI tooling. The focus remains on habits and patterns that scale from solo engineers to professional engineering teams.

Languages: This session can be delivered in both Dutch and English.
Target Audience: PowerShell users in general and among others: DevOps Engineers, Infrastructure Engineers, Cloud Engineers.
Technical Requirements: Familiarity with basic PowerShell scripting
Preferred Duration: 45-60 minutes.
Additional Notes: Live demo included, with resources and scripts available for download.