Lesson 8 of 10 · About 5 minutes

Privileged and service access

Learn the concept.

Privileged accounts can make powerful changes. Workload accounts run services and need identifiable ownership, even though no person signs in as the workload.

Limit privileged use

Use named administrative identities and controlled elevation where supported. Keep ordinary work separate from administrative tasks.

Assign workload owners

Document what the service does, what access it needs, and who maintains it. Avoid dependence on a departing employee’s personal account.

Review credentials and access

Prefer managed or short-lived credentials where practical. Review privileges and rotate or revoke credentials using an approved process.

Field example08 / A

Put it in context

A scheduled reporting job runs under a dedicated identity with access to its dataset. Its owner and permissions are documented, so a staff departure does not orphan it.

SEE THE IDEA

Different identities. Clear accountability.

Illustrative administrative and automated work.

  1. Human administrator

    Named administrative identity, controlled elevation where supported, and separation from ordinary work.

  2. Reporting workload

    Dedicated identity, documented owner and purpose, narrow dataset access, and managed or short-lived credentials where practical.

Neither category should depend on an undocumented shared password. Review both privileges and ownership.
Read the visualWhat prevents a staff departure from orphaning the reporting job?

Documented workload ownership, a maintained dedicated identity, and an approved ownership-transfer process.

Make a decision.

Use what you just learned. A correct answer lets you save this lesson to your progress.

Take this with you.

Powerful and non-human accounts need narrow access and clear ownership.

YOUR LEARNING SPACE