liveBook · Manning

Subject

A subject is an entity designated as the focus of representation, data modeling, or an authorization policy.

How 3 Manning books explain it

Grokking Relational Database Design

A subject is a person, place, thing, event, or other real-world item identified as relevant to a database design.

How it is used
Identifies real-world items during requirements gathering so designers can capture characteristics and relationships.
How deep it goes
Defines subjects and maps them to entities, stopping short of detailed database implementation.
Examples
Uses people, places, things, events, and an employee-to-entity conversion as examples.
What you can do after
Understand how to identify relevant subjects and translate them into entities with attributes.

Read how Grokking Relational Database Design explains subject →

Fundamentals of Cybersecurity

A subject is an individual, application, service, device, or other active entity that requests or attempts to access a resource.

How it is used
Frames access-control decisions around the active entity requesting a resource.
How deep it goes
Defines subjects as active entities and distinguishes them from passive objects within the access-control framework.
Examples
Uses users, applications, scripts, database queries, workstations, smartphones, and network-connected devices as subjects.
What you can do after
Evaluate access requests by identifying the requesting entity before applying authentication, authorization, and access rules.

Read how Fundamentals of Cybersecurity explains subject →

Authorization in Action

A subject is the entity referred to in an account, policy, or authorization decision, potentially referring to a principal or resource.

How it is used
Clarifies who an account, policy, or authorization decision refers to, especially when requester and affected entity differ.
How deep it goes
Defines subject, contrasts it with principal, and shows attribute-based treatment in XACML without developing a typed subject model.
Examples
Uses parent-on-behalf-of-child access and XACML attributes such as username, department, and clearance.
What you can do after
Evaluate authorization terminology and distinguish the requester from the entity represented in a policy or access decision.

Read how Authorization in Action explains subject →

Also covered in

What to know first

Related concepts

Questions about subject

What is subject?

A subject is an entity designated as the focus of representation, data modeling, or an authorization policy.

Which Manning books explain subject?

Grokking Relational Database Design, Fundamentals of Cybersecurity and Authorization in Action.

What should I know before learning subject?

Manning books that teach subject usually introduce authentication and user ID first.

What is the difference between subject and principal?

A subject is an entity designated as the focus of representation, data modeling, or an authorization policy. A security principal is an identity representing an entity that can be authenticated or granted permissions in a security system.

What is subject a kind of?

Subject is a kind of entity. An entity is a distinct, identifiable object, concept, participant, or record represented in a system's model or data.

What is subject part of?

Subject is part of prompt. A prompt is text or other input supplied to an AI model to provide instructions, context, or other information that guides its response or generated output.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.