Course contentsShow
← Security
Lesson 1429 of 3,05229. Operating System Security - HardeningFree lesson

Windows Access Tokens and Permissions

Understanding Windows security principals, access tokens, and NTFS permission inheritance.

Windows Access Tokens and Permissions

What You'll Learn

You'll learn how Windows uses access tokens to represent user identity and enforce permissions on files and resources.

The Core Concept

When you log into Windows, the system creates an access token — think of it as a digital badge that contains your identity credentials. This token holds your user ID (SID), group memberships, and privileges. Every process you launch carries a copy of this token, allowing Windows to check "does this person have permission?" before allowing any action.

Security Principals

A security principal is any entity that can be authenticated: users, computers, or services. Each gets a unique Security Identifier (SID). When you create a file or folder, Windows stamps it with your SID as the owner.

Access Tokens Explained

Your access token is like a passport that travels with every program you run. It contains:

  • Your user SID
  • Group SIDs (like "Administrators" or "Users")
  • Privilege list (rights like "shut down system" or "debug programs")
  • Integrity level (for User Account Control)

NTFS Permission Inheritance

NTFS permissions flow down the folder tree by default. When you set "Read" permission on C:\Projects, all subfolders and files inherit it automatically — unless you explicitly break inheritance. This cascading model simplifies administration: secure the parent, protect the children.

Permissions are either explicit (set directly on an object) or inherited (flowing from a parent). Explicit permissions always take precedence over inherited ones.

The Permission Check

When you try to open a file, Windows compares your token's SIDs against the file's Access Control List (ACL). The ACL contains Access Control Entries (ACEs) listing who can do what. If your token matches an allowed ACE and no deny ACE blocks you, access is granted.

Key Takeaway: Windows access tokens carry your identity credentials through every action, while NTFS permission inheritance creates cascading security boundaries that enforce who can access what based on ACL comparisons.