Azure Security Flashcards
What are Security Principals in Azure Identity Management?
A security principal is any entity that can be authenticated by the operating system, such as a user account, a computer account, or a thread or process that runs in the security context of a user or computer account, or the security groups for these accounts.
What is a Security Identifier (SID)?
Security identifiers (SIDs) provide a fundamental building block of the Windows security model. They work with specific components of the authorization and access control technologies in the security infrastructure of the Windows Server operating systems. A SID is a value of variable length that’s used to uniquely identify a security principal that represents any entity that can be authenticated by the system.
What are Security Descriptors in Azure Identity Management?
A security descriptor is a data structure that’s associated with each securable object. All objects in Active Directory and all securable objects on a local computer or on the network have security descriptors to help control access to the objects. Security descriptors include information about who owns an object, who can access it and in what way, and what types of access are audited. Security descriptors contain the access control list (ACL) of an object, which includes all the security permissions that apply to that object.
What are the two types of ACLs in Azure Identity Management?
- DACL (Discretionary ACL)
- SACL (System ACL)
What is an Application Object?
A Microsoft Entra application is defined by its one and only application object. The application object resides in the Microsoft Entra tenant where the application was registered (known as the application’s “home” tenant). An application object is used as a template or blueprint to create one or more service principal objects.
What does a Application Object of a Microsoft Entra tenant application describe?
- How the service can issue tokens
- Resources that the application might need access
- Actions that the application can take
What is a Service Principal Object?
To access resources secured by a Microsoft Entra tenant, the entity that requires access must be represented by a security principal. This is true for both users (user principal) and applications (service principal). The security principal defines the access policy and permissions for the user/application in the Microsoft Entra tenant.
What are the 3 types of Service Principals?
- Application
- Managed Identity
- Legacy
What is an Application type of Service Principal?
This type of service principal is the local representation, or application instance, of a global application object in a single tenant or directory. A service principal is created in each tenant where the application is used and references the globally unique app object.
What is a Managed Identity?
This type of service principal is used to represent a managed identity. Managed identities provide an identity for applications to use when connecting to resources that support Microsoft Entra authentication. When a managed identity is enabled, a service principal representing that managed identity is created in your tenant.
What is a Legacy Service Principal?
This type of service principal represents a legacy app, which is an app created before app registrations were introduced or an app created through legacy experiences. A legacy service principal can have credentials, service principal names, reply URLs, and other properties that an authorized user can edit, but doesn’t have an associated app registration.
What are the different types of managed identites?
- System Assigned
- User Assigned
What is the relation between Application Object and Service Principal?
The application object is the global representation of your application for use across all tenants, and the service principal is the local representation for use in a specific tenant.
What are the different types of Permissions?
- Delegated-access
- App-only access
What are the different types of consents?
- static user consent
- incremental and dynamic user consent
- admin consent