---
title: "Discussion on \"Breaking and Hardening Azure Workload Identities: From Long-Lived Secrets to GitHub OIDC Federation\" | Hashnode"
description: "Discussion on \"Breaking and Hardening Azure Workload Identities: From Long-Lived Secrets to GitHub OIDC Federation\". Replacing a client secret with OIDC does not automatically give you least privilege.\nIt solves one important problem:\n\nHow does the workload authenticate?\n\nIt does not automatically solve another equa"
url: "https://hashnode.com/posts/breaking-and-hardening-azure-workload-identities-from-long-lived-secrets-to-github-oidc-federation/6aa29e99a6522423c99ec5c2"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Breaking and Hardening Azure Workload Identities: From Long-Lived Secrets to GitHub OIDC Federation](https://azurepj.hashnode.dev/breaking-and-hardening-azure-workload-identities-from-long-lived-secrets-to-github-oidc-federation?utm_source=hashnode&utm_medium=feed)

Replacing a client secret with OIDC does not automatically give you least privilege. It solves one important problem: How does the workload authenticate? It does not automatically solve another equa

Sep 10 · 20 min read · azurepj.hashnode.dev  
Read the article

-   [#azure](https://hashnode.com/tag/azure)
-   [#cybersecurity](https://hashnode.com/tag/cybersecurity)
-   [#terraform](https://hashnode.com/tag/terraform)
-   [#github-actions](https://hashnode.com/tag/github-actions)

## Written by

[Sesank Munukutla (Naga)](https://hashnode.com/@nagasesank)

@nagasesank · Hyderabad India

  
[View profile](https://hashnode.com/@nagasesank)

Cybersecurity Engineer

Cyber Security Engineer skilled in AWS, Palo alto, GRC and Healthcare Management

## Responses

Markdown supported · ⌘↵ to post

No responses yet.