How Secure Can You Be?
summary
Discussion centers on concrete credential-handling choices for PowerShell scripts that must run under other accounts: risks of plain-text credentials, prompting versus re-invoking with supplied creds, storing a SecureString or using Export-Clixml or DPAPI-wrapped files, packaging with PrimalScript/PowerShell Studio, attaching ACLs to key files, or enforcing access via constrained endpoint or backend service (IIS/OData or orchestrator vault). Decision factors are scale, frequency of password rotation, attack surface if exposed, and operational overhead to manage keys.
AI-written summary · about
chapters (7)
- 0:00Secure PowerShell usage
- 10:43Credential management challenge
- 17:54Security versus usability trade-offs
- 27:11Credential storage and access methods
- 32:50Beyond traditional credentials
- 36:12Balancing security controls
- 37:13Closing thoughts
related talks
48mStop Writing Insecure PowerShell... Seriously.
44mSecrets at Scale: Managing Cloud Credentials with PowerShell Automation
57mSecuring PowerShell: Hands-On Lab
49mPowerShell for Security Incident Response
46mSecrets Management for the Modern Tech. Pro
43mSecure Development
55mOffensive Azure Security
43mSecuring your Environment with Just Enough Administration