<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Group Managed Service Account on LEIKAH</title><link>https://leikah.haoyingcao.xyz/en/tags/group-managed-service-account/</link><description>Recent content in Group Managed Service Account on LEIKAH</description><generator>Hugo</generator><language>en</language><atom:link href="https://leikah.haoyingcao.xyz/en/tags/group-managed-service-account/index.xml" rel="self" type="application/rss+xml"/><item><title>Group Managed Service Account</title><link>https://leikah.haoyingcao.xyz/en/docs/active_directory/movement/acl_abuse/gmsa/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://leikah.haoyingcao.xyz/en/docs/active_directory/movement/acl_abuse/gmsa/</guid><description>&lt;p&gt;The need to protect service accounts against attacks such as Kerberoasting gave rise to &lt;strong&gt;Managed Service Accounts (MSA)&lt;/strong&gt; and later &lt;strong&gt;Group Managed Service Accounts (gMSA)&lt;/strong&gt;. While both supports automatic password generation and rotation, the latter allows the same service accounts to be used acrossed different machines.&lt;/p&gt;
&lt;p&gt;Members of the group that manage the gMSA are intended to be the machine accounts of the computers where the service account will be deployed on. Members have the ability to read the password hash of the service account (&lt;code&gt;ReadGMSAPassword&lt;/code&gt;).&lt;/p&gt;</description></item></channel></rss>