A directory schema property set for account details that are intended to be broadly visible within an organisation. In Active Directory, a property set groups related attributes and controls who can read or write them as a unit, which simplifies delegated administration and access control over user data.
What the Public-Information Property Set Does
A public-information property set is an Active Directory schema grouping that bundles related account attributes under one access-control boundary. It matters because directory administrators can delegate read or write permissions to a coherent set of fields instead of managing each attribute individually, which keeps administration simpler and policy decisions more consistent.
Property sets are not just organisational labels. They are part of how directory data is exposed, modified and governed at scale, especially when different teams need controlled visibility into user details. That makes the set an access-control abstraction, not a security control by itself.
Why Property Sets Matter in Directory Security
In a directory, broad account data is often needed by help desk staff, HR systems, identity workflows and other internal consumers. Grouping those attributes into a property set makes it easier to apply a shared permission model and reduce the chance that one field is left outside the intended policy. It also helps avoid inconsistent delegation across similar attributes.
The security value comes from reducing permission sprawl. Instead of assigning separate rights to many attributes, the directory can treat a defined bundle as the unit of control. That is useful when organisations want predictable read access for widely visible data while still keeping sensitive attributes in narrower sets.
For practitioners, the important distinction is that the property set defines a boundary in the schema, while the actual exposure still depends on who has been granted access. A well-named set does not prevent overexposure if the delegated permissions around it are too broad.
How Access Is Evaluated and Delegated
When a property set is used, administrators usually think in terms of who should read or update the grouped attributes, what administrative role needs that access, and whether the same permission should apply across all accounts. That makes the set useful for standardising delegation in environments where attribute-by-attribute control would be hard to sustain.
It is also important to understand inheritance and role design. If a role or group can write to the set, it can affect every attribute contained in that set, so the grouping decision influences operational blast radius. If the set contains only broadly visible information, that may be acceptable; if it later grows to include more sensitive fields, the delegation model may become too permissive.
In practice, property sets sit alongside broader access-control concepts such as least privilege and role-based delegation. Their value is highest when the schema grouping reflects a stable business need, rather than a convenient but loosely defined collection of attributes.
Operational and Governance Implications
Property sets are especially relevant to directory governance because they shape how account data is classified, exposed and maintained over time. If the ownership of the set is unclear, teams may add attributes to it without reviewing the access impact, which can quietly expand who can see or change information.
They also affect administration quality. A property set that is too narrow forces duplicate permission work, while one that is too broad can flatten distinctions between routine account data and more sensitive identity attributes. Good governance therefore depends on keeping the set aligned to an explicit data classification and delegation model.
For a directory service, the real design question is not whether a property set exists, but whether it still matches the organisation’s intended visibility boundary for the data it contains. That boundary should be reviewed whenever schema, business ownership or access patterns change.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5 sets the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | AC-6 — Least Privilege | Property sets support scoped attribute access, which directly implements least-privilege delegation. |
| IA-5 — Authenticator Management | Directory attribute exposure often includes account details tied to credential and identity administration. | |
| Recommendation — Limit attribute access to the smallest permission set that still supports the delegated directory function. Control credential-related directory attributes with tightly scoped administrative access and lifecycle handling. | ||
| ISO/IEC 27001:2022 | A.5.15 — Access control | Property sets are a directory access-control boundary used to manage read and write permissions. |
| A.5.16 — Identity management | Delegating access to account-property bundles depends on governed identity administration. | |
| A.5.18 — Access rights | Property-set permissions are access rights that must be granted, reviewed and revoked consistently. | |
| Recommendation — Define and review attribute-level access rules for each directory property set. Assign ownership for directory attribute access and keep delegation rules aligned to identity administration. Periodically review who can read or modify each directory property set. | ||
Related resources from NHI Mgmt Group
- How should organisations prepare enterprise data for AI use without exposing sensitive information to public LLMs?
- How should security teams set up remote desktop access so it stays simple without exposing devices to the public internet?
- Why does the High level of ENS require stronger controls for critical public sector information?
- How should financial institutions implement GLBA safeguards for non-public personal information across access, encryption, and monitoring?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org