High disk usage by Antimalware Service Executable

Windows Defender High Cpu Usage in CI/CD pipelines is often a secret management failure — credentials expired, rotated without updating the pipeline, or accidentally logged and revoked. Secure secret handling in pipelines requires both the right tooling and the right practices. Never store secrets as plain text in configuration files committed to version control — use environment variables injected by the CI platform's secret store (GitHub Actions Secrets, GitLab CI/CD Variables, CircleCI Context Variables). Secrets stored in CI platforms are masked in logs, so they are not printed even when accidentally referenced in echo statements. Rotate secrets on a schedule: short-lived OIDC tokens (GitHub Actions' native AWS integration) eliminate rotation entirely. For database credentials in CI test pipelines, use ephemeral test databases provisioned per-run (testcontainers, GitHub Actions service containers) rather than shared credentials to a persistent database. When Windows Defender High Cpu Usage appears after a deployment or secret rotation, check whether the affected service has a cached copy of the old credential — restart the service or clear the credential cache after rotating to ensure the new credential is picked up.