Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
An access package bundles the groups, applications, and roles a person needs for a job into one requestable item, with an approver, an expiry date, and a recorded justification.

What Are Access Packages?
Ask most organisations how a new analyst gets the eleven things they need on day one and the honest answer involves a ticket, a manager, and somebody in IT copying permissions from a colleague who happens to sit nearby. An access package replaces that with a named bundle: the groups, application roles, and SharePoint sites that go with a job, offered as a single item that a person can request, an owner can approve, and the platform will take away again on a date you set in advance.
The discipline is called entitlement management. Microsoft Entra ID is the implementation most UK organisations meet first, but SailPoint, Saviynt, and Okta Identity Governance all provide the same construct under different names.
A package has four moving pieces, and the security value comes from the last two rather than the first two.
Cloning an existing user’s permissions is the single most effective mechanism for spreading privilege creep through an organisation. The colleague being copied has three years of accumulated access from two previous roles. All of it transfers, nobody notices, and within a few cycles the finance team has write access to systems that no one in finance has needed since 2021.
Access packages break that chain because the unit of request is a job function rather than a person. When an attacker compromises an ordinary account—through credential stuffing, a phished session token, or a push fatigue attack—what they inherit is bounded by what that job genuinely requires. That is the principle of least privilege expressed as a workflow rather than a slide.
External access is where packages earn their keep fastest. A partner organisation can be allowed to request a package, their own sponsor approves it, the guest account is created automatically, and when the sixty-day term ends the account is removed along with every grant it carried. No one has to remember the consultancy finished in March.
Compare that with the usual pattern. Guest accounts in a mature tenant frequently outnumber internal ones, a large share have not signed in for over a year, and many were invited by someone who has since left. Those accounts remain valid identities in your directory, subject to whatever conditional access you apply—which, for guests, is often less than you apply to staff.
The most common failure is granularity. Build one package per application and you have recreated the ticket queue with extra steps; build one package per department and you have recreated the over-privileged clone. Aim at job functions that a line manager would recognise—“Payroll Administrator”, “Third-Line Support, EMEA”—and accept that a few people will need two packages.
Three practical rules help. First, package owners should be the business owners of the resource, not the identity team, because they are the only people who can judge whether a request is legitimate. Second, set a duration on everything; perpetual packages quietly become standing privilege. Third, keep privileged roles out of packages entirely and route them through privileged identity management with activation, approval, and a time limit measured in hours.
For UK organisations, the reporting matters as much as the control. ISO 27001 Annex A 5.18 expects access rights to be provisioned, reviewed, and removed according to a defined policy, and an entitlement management catalogue answers that with evidence rather than assertion: who requested what, who approved it, on what grounds, and when it was taken away.
At Privia Security, we review entitlement design and joiner-mover-leaver flows as part of our infrastructure and architecture review services.
A security group is a container of members. An access package is a governed request for a set of resources, which may include several groups plus application roles and sites. The difference is the wrapper: a package carries an approval policy, a justification, an expiry date, and a review cycle. Groups have none of that unless you build it separately.
No, they sit on top of it. Role-based access control defines what a role may do inside an application; entitlement management decides who is allowed to hold that role, for how long, and who signed it off. Most organisations use both, with packages bundling several application roles that a single job function needs.
Pick a job function with a clear owner, high turnover, and obvious boundaries, such as a service desk or a contact centre role. Those give you fast feedback on whether the catalogue design works. Avoid starting with privileged administration or with anything whose access list is currently disputed, because the governance argument will stall the rollout.
Yes, and this is one of the strongest use cases. A policy can allow users from specified partner domains to request a package, trigger guest account creation on approval, and remove both the grants and the guest account when the term expires. It gives external access a defined end date instead of relying on someone remembering to clean up.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.