Interactive Training Guide

Service Accounts
Management Module

A comprehensive training on Delinea's dedicated SAM module β€” covering automated discovery, intelligent dependency mapping, structured onboarding workflows, and continuous rotation compliance across your enterprise service account estate.

7
Modules
~45
Min Duration
7
Knowledge Checks
πŸ”

What is the Service Accounts Management Module?

Delinea's SAM module is a purpose-built component within the Privileged Access Management (PAM) platform dedicated exclusively to the lifecycle governance of non-human, machine identities β€” commonly called service accounts. These accounts authenticate applications, services, scheduled tasks, and integrations across enterprise environments, yet historically lacked the visibility and control applied to human user accounts.

🎯

The Core Problem

Service accounts proliferate silently β€” often created ad hoc, shared across teams, never rotated, and rarely decommissioned. They become the attacker's preferred lateral movement path.

Risk Reduction
βš™οΈ

Dedicated Module

SAM is not bolted onto credential vaulting. It is a standalone module with purpose-built workflows, discovery engines, and reporting tuned specifically for non-human identity patterns.

Purpose-Built
πŸ”„

Full Lifecycle

From initial discovery through onboarding, rotation scheduling, and eventual decommissioning β€” SAM governs the full service account lifecycle without operational disruption.

End-to-End
πŸ“‹

Audit & Compliance

Every rotation event, approval decision, and policy exception is logged with immutable audit trails satisfying SOX, PCI-DSS, NIST 800-53, and CIS control requirements.

Compliance Ready

Key Differentiator: Dependency Awareness

Unlike traditional vaulting solutions, SAM understands where service accounts are used before rotating credentials. The automated dependency detection engine scans Windows Services, Scheduled Tasks, IIS Application Pools, COM+ applications, and ODBC data sources β€” preventing outages that have historically blocked rotation programs from launching.

// Knowledge Check

What distinguishes Delinea's SAM module from traditional credential vaulting solutions?
βœ“ Correct. Dependency awareness β€” scanning services, tasks, IIS pools and more before rotation β€” is the critical differentiator that prevents outages and allows rotation programs to scale.
βœ— Not quite. The key differentiator is automated dependency detection before credential rotation, which prevents application outages that block most rotation programs from scaling.
πŸ—οΈ

The SAM module operates as a layered system with clear separation between the presentation tier, the orchestration engine, the integration fabric, and the data persistence layer. Click any component below to learn more.

Presentation
SAM Console Web UI + REST API
Reporting Engine Compliance Dashboards
Notification Hub Email / SIEM / ITSM
↕ API calls
Orchestration
Workflow Engine Approval Orchestration
Rotation Scheduler Frequency Management
Policy Engine Rules & Exceptions
↕ Task dispatch
Integration
AD Connector LDAP / Kerberos
Dependency Scanner Agentless / Agent
Rotation Agent Credential Propagation
↕ Encrypted storage
Persistence
Secret Vault AES-256 at rest
Audit Log Store Tamper-Evident
Config Database Account Metadata
Click any component in the architecture diagram above to see a description of its role and responsibilities within the SAM module.
🌐

Deployment Models

SAM supports on-premises, cloud-hosted (SaaS), and hybrid deployment models. The Delinea Platform Server acts as the control plane in all configurations.

Flexible
πŸ”’

Security Boundaries

All inter-component communication is mutually authenticated via TLS 1.3. Credentials in transit are never stored in plaintext; vault operations use HSM-backed key management where available.

Zero Trust
πŸ“‘

High Availability

The orchestration tier is stateless and horizontally scalable. Vault nodes support active-active clustering with synchronous replication, targeting 99.99% availability SLAs.

Enterprise Grade
πŸ”

Why Continuous Discovery Matters

Point-in-time manual inventories become stale within days. Delinea's AD Connector maintains a real-time synchronized view of service accounts by monitoring LDAP change notifications, periodic deep scans, and event-driven triggers. New accounts surface automatically; no ticket required to initiate visibility.

AD Discovery Simulator

[00:00:00] SAM AD Connector ready. Click "Run Discovery Scan" to simulate.
β€”
Accounts Found
β€”
New (Unmanaged)
β€”
Stale (90d+)
β€”
High Risk
⚑

Change Notification Listening

SAM subscribes to LDAP DirSync and USN-based change notifications, surfacing new service accounts within minutes of creation β€” not days.

Near Real-Time
🌲

Multi-Forest Support

A single SAM instance can monitor multiple AD forests and domains simultaneously, consolidating visibility across complex enterprise topologies including trusts.

Enterprise Scale
🏷️

Automatic Classification

Discovered accounts are automatically tagged by type (service account, gMSA, sMSA, computer account) using pattern matching against naming conventions and attribute analysis.

ML-Assisted
🚦

Risk Scoring

Each discovered account receives a risk score based on last password change date, SPN configuration, delegation settings, group membership, and password-never-expires flags.

Risk-Based

⚠️ Discovery vs. Management

Discovery surfaces accounts into SAM's inventory with read-only visibility. Accounts are not automatically enrolled for rotation β€” that requires explicit onboarding through the approval workflow. This ensures operational teams are not surprised by credential changes to unknown accounts.

// Knowledge Check

When SAM discovers a new service account via AD integration, what happens next by default?
βœ“ Correct. Discovery provides visibility β€” not automated action. Onboarding through the approval workflow is required before SAM manages rotation.
βœ— Incorrect. By default, discovered accounts are added to inventory with read-only visibility. No credential changes occur until the account is explicitly onboarded through the approval workflow.
πŸ•ΈοΈ

The Rotation Outage Problem β€” Solved

The #1 reason enterprises fail to rotate service account passwords is fear of outage. If svc_payments is used by 4 Windows Services, 2 Scheduled Tasks, and an IIS Application Pool β€” rotating its password without updating all 7 dependency configurations causes immediate failures. SAM's Dependency Detection engine automatically maps all usages before any rotation attempt.

Dependency Map β€” Click an account to expand

πŸͺŸ

Windows Services

SAM remotely queries the Windows Service Control Manager on enrolled endpoints to identify services running under the target account's credentials.

SCM API
πŸ“…

Scheduled Tasks

Task Scheduler XML definitions are parsed across domain-joined machines to identify tasks configured with explicit credential context for the service account.

Task Scheduler
🌍

IIS Application Pools

IIS metabase and WMI queries identify application pools using custom identity configurations that reference the target service account credentials.

IIS / WMI
πŸ—„οΈ

Database Logins

SQL Server and Oracle instances are queried for login mappings and linked server configurations that authenticate using the target service account.

SQL / Oracle

Automatic Dependency Update During Rotation

Once dependencies are mapped, SAM's rotation agent doesn't just change the AD password β€” it propagates the new credential to every detected dependency in the correct sequence, using WMI, DCOM, or agent-based channels. Services are restarted in the right order. The entire process is atomic: if any dependency update fails, the rotation rolls back and alerts fire.

βœ…

Click each workflow step to expand its details. The onboarding workflow enforces a structured review process ensuring no account is brought under SAM management without appropriate stakeholder approval and technical validation.

1

Discovery & Intake

SAM's AD Connector surfaces the account in the Unmanaged Accounts queue with auto-populated metadata including SPN details, group memberships, last logon, and password age.

The intake record includes: sAMAccountName, distinguished name, account type classification, password last set date, pwdNeverExpires flag, logon workstation restrictions, delegated permissions, and initial risk score. No human action is required at this stage.
Automated Read-Only
2

Owner Assignment

An application owner or service team lead is designated as the account custodian. SAM can suggest owners based on AD OU structure, group membership, and historical usage patterns.

Owner assignment can be manual (security admin selects from AD groups), semi-automated (SAM suggests based on heuristics and admin confirms), or policy-driven (all accounts in a specific OU are automatically assigned to an owning group). Owner receives notification with accountability statement.
Manual or Automated Notified
3

Dependency Scan

Before any approval proceeds, SAM runs a full dependency scan against all enrolled endpoints to build a complete map of services, tasks, and applications using the account.

The dependency scan results are attached to the approval request as a pre-rotation impact assessment. Approvers can see exactly what will be affected. If unknown dependencies are found (endpoints not yet enrolled), the workflow flags them as requiring manual verification before progression.
Automated Scan Blocking
4

Security Review & Approval

The onboarding request β€” with full metadata, risk score, dependency map, and proposed rotation policy β€” is routed to one or more approvers based on configurable approval routing rules.

Approval tiers can be configured: single approver (low-risk accounts), dual approval (privileged accounts), or escalating approval (high-risk requiring CISO sign-off). Time-based SLAs enforce response deadlines; unacknowledged requests escalate automatically. Approvers access requests via SAM console or email deep links.
Multi-Tier SLA Enforced Audited
5

Policy Configuration

Upon approval, the account owner and security team configure the rotation policy: frequency, maintenance window, notification recipients, and rollback parameters.

Policy parameters include: rotation frequency (daily/weekly/monthly/quarterly/custom), time-of-day window, blackout dates, number of previous passwords retained, failure escalation contacts, and whether manual approval is required before each rotation or rotations are fully automated.
Configurable Policy-Driven
6

Vault Enrollment & First Rotation

SAM vaults the current credential, executes the first managed rotation (with full dependency propagation), and transitions the account to Managed status in the compliance dashboard.

The initial rotation runs in a controlled window with pre-rotation health checks (ping all dependent services), the actual rotation with synchronized dependency updates, post-rotation validation (confirm all services are running), and automatic rollback if validation fails within the configured timeout window (default: 5 minutes).
Managed Validated Rollback Ready

// Knowledge Check

During the onboarding approval workflow, at what stage does the dependency scan occur β€” and why is its timing significant?
βœ“ Correct. The dependency scan runs before approvers review the request, giving them full impact visibility. Approvers should never approve an onboarding without knowing what will be affected by future rotations.
βœ— Not quite. The scan occurs before the approval review (Step 3 of 6), so approvers receive the complete dependency impact assessment as part of the approval request. This is a deliberate design choice to ensure informed approval decisions.
πŸ•

Not All Service Accounts Are Equal

A privileged domain admin service account running a nightly replication task demands different rotation urgency than a low-privilege read-only monitoring account. SAM's rotation scheduler allows granular frequency configuration by account type, risk tier, OU, or individual account β€” while the compliance dashboard surfaces deviations from policy.

Account Type Default Frequency Risk Tier Recommended Window Override
Domain Admin Service Accounts 30 Days Critical Weekends 02:00–04:00 local
Privileged App Service Accounts 60 Days High Weekdays 23:00–01:00 local
Standard App Service Accounts 90 Days Medium Weekends 01:00–05:00 local
Read-Only / Monitoring Accounts 180 Days Low Any maintenance window
Group Managed Service Accounts (gMSA) 30 Days (AD-managed) Managed Automatic β€” KDC controlled
External / Service Principal Accounts 90 Days Medium Weekends, coordinated with vendor
πŸ“†

Blackout Windows

Define date ranges when rotations are prohibited β€” fiscal year-end, peak trading periods, or holiday freezes. SAM reschedules affected rotations automatically and flags accounts that become overdue during blackouts.

Change Freeze
🧩

Dependency-Aware Sequencing

When an account serves multiple services across servers, the scheduler calculates the optimal update sequence to minimize service restart time and avoid circular dependencies.

Smart Ordering
πŸ””

Pre-Rotation Notifications

Account owners and on-call teams receive configurable advance notice (default: 48 hours) before each rotation, with a direct link to defer or approve if manual confirmation mode is enabled.

Advance Notice
↩️

Automatic Rollback

If any post-rotation health check fails, SAM automatically restores the previous credential and dependency configurations within the rollback timeout window, then escalates an alert to operations.

Self-Healing

// Knowledge Check

An organization enters a 2-week fiscal year-end freeze during which no service account rotations may occur. Three accounts are scheduled to rotate during this period and will exceed their policy limit. How does SAM handle this scenario?
βœ“ Correct. Blackout windows reschedule rotations and the compliance dashboard shows a distinct "Overdue – Blackout Exception" status, allowing auditors to see these are policy-acknowledged deferrals, not compliance failures.
βœ— Incorrect. SAM respects blackout windows by rescheduling rotations to after the freeze and marking them with a "Blackout Exception" status on the dashboard. This maintains compliance visibility without forcing risky changes during sensitive periods.
πŸ“Š
Rotation Coverage Rate
β€”
↑ 12% vs. 90 days ago
Overdue Rotations
23
↑ 4 since last week
Critical Overdue (>2Γ— policy)
7
Requires immediate action
Managed Accounts
312
↑ 28 this month
Avg. Days Since Last Rotation
41
Across all managed accounts
Unmanaged Discovered
89
Awaiting onboarding

Rotation Coverage by Account Type

Last updated: today
Domain Admin Service Accounts 94%
Privileged App Service Accounts 87%
Standard App Service Accounts 76%
Read-Only / Monitoring Accounts 61%
External / Service Principal 42%

Overdue Rotation Alerts

Account Type Policy Limit Days Overdue Severity Action
svc_sql_prod@corp.local Privileged App 60 days 127 days ● Critical
svc_erp_batch@corp.local Standard App 90 days 98 days ● Critical
svc_reports_ro@corp.local Read-Only 180 days 214 days ● High
svc_exchange_mgmt@corp.local Privileged App 60 days 73 days ● High
svc_sharepoint@corp.local Standard App 90 days 97 days ● Medium
πŸ“€

Export & Reporting

Generate point-in-time compliance snapshots in PDF, CSV, or JSON format. Pre-built templates exist for SOX 404, PCI-DSS 8.3, NIST 800-53 AC-2, and ISO 27001 A.9.2 control requirements.

Audit Ready
πŸ”—

SIEM Integration

Rotation events, overdue alerts, and approval decisions stream to Splunk, Microsoft Sentinel, or any CEF/Syslog target in real time. Dashboards can be built using the pre-built SPL/KQL packs.

SIEM Streaming
πŸ“§

Scheduled Digest Reports

Configure weekly or monthly email digests for account owners, team leads, and CISO recipients, summarizing rotation status, upcoming scheduled rotations, and outstanding onboarding queues.

Automated Reporting

// Knowledge Check

On the compliance dashboard, what does the "Rotation Coverage Rate" metric specifically measure?
βœ“ Correct. Rotation Coverage Rate = (accounts rotated within policy window) Γ· (total managed accounts). It answers: "Of all the accounts we're managing, what fraction are compliant with their rotation schedule right now?"
βœ— Incorrect. Coverage Rate measures the fraction of managed accounts whose credentials are current within their configured policy window β€” not success rates or discovery percentages.
Training Module v4.2 Β· For internal use and authorized partner training only
Β© 2024 Delinea Inc. All rights reserved.
Complete all 7 modules to receive course credit