In LDAP (Microsoft Active Directory) the ObjectSID contains the Security Identifier is displayed as a SID string value for the Security Identifier of the LDAP Entry.
Each time a user logs on, the system retrieves the Security Identifier for that user from the database and places it in the access token for that user.
The system uses the Security Identifier in the access token to identify the user in all subsequent interactions with Windows security.
When a Security Identifier has been used as the Unique Identifier for a Security Principal Objects (user or group), it cannot ever be used again to identify another Security Principal Object.
Windows security uses Security Identifiers in the following security elements:
For example, the Well-known Security Identifiers, Everyone and World, identify a group that includes all users.
Most applications never need to work with SIDs.
Because the names of well-known Security Identifiers can vary, you SHOULD use the functions to build the Security Identifier from predefined constants rather than using the name of the well-known SID.
For example, the U.S. English version of the Microsoft Windows has a well-known Security Identifier named "BUILTIN\Administrators" that might have a different name on international versions of the system.
S-1-5-21-4064627337-2434140041-2375368561-1036
All SID fields have a specific meaning; so, for the above sample SID:
The SID of an AD DOMAIN account is created by a domain's security authority that runs on every Windows Domain Controller (DC). The SID of a local account is created by the Local Security Authority (LSA) service that runs on every Windows box.
An important property of a SID is its uniqueness in time and place. A Security Identifier is unique in the environment where it was created (in a domain or on a local computer). It's also unique in time: If you create a user object, delete it, then recreate it with the same name, the new object won't have the same SID as the original object.