Study guide

11.2 Central Credential Provider (CCP) & Web Service Integration

CyberArk Defender - PAM PAM-DEF

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Vault Architecture, Network & Security

1.1 CyberArk PAS Core Architecture & Component Topology 1.2 Vault OS Hardening, Network Isolation & Port Requirements 1.3 Vault Cryptography, Encryption Keys & Master User Recovery

2 Chapter 2: Vault Configuration, Administration & CLI Utilities

2.1 Vault Server Configuration Files & DBParm.ini Tuning 2.2 Vault Administrative Utilities & PARClient Commands 2.3 Event Notification Engine (ENE) & Notification Administration

3 Chapter 3: Password Vault Web Access (PVWA) Administration

3.1 PVWA Web Portal Architecture & Interface Configuration 3.2 PVWA REST API Administration & Lifecycle Automation 3.3 PVWA Security Settings, User Access & Session Timeouts

4 Chapter 4: Central Policy Manager (CPM) Architecture & Operations

4.1 CPM Service Architecture, Logs & Multi-CPM Load Distribution 4.2 The Credential Management State Machine: Change, Verify & Reconcile 4.3 CPM Plug-in Architecture, Process/Prompts Files & Custom Plug-in Troubleshooting 4.4 Loosely Connected Devices: Rotating Laptop & Workstation Credentials

5 Chapter 5: Safe Design, RBAC & Account Governance

5.1 Enterprise Safe Architecture & Naming Conventions 5.2 Safe Permissions, Authorizations & Safe Handler Delegation 5.3 Object Versioning, Retention Policies & Storage Quotas 5.4 Mandatory Account Properties, Account Types & Linked Accounts 5.5 Vault Users, Predefined Groups & Vault-Level Authorizations

6 Chapter 6: Account Discovery & Lifecycle Workflows

6.1 Automated Account Discovery, Detection Rules & Pending Accounts 6.2 Dual Control Workflows, Multi-Level Approvals & Master Approver 6.3 Exclusive Access, One-Time Passwords (OTP) & Check-out Automation 6.4 Bulk Onboarding: Password Upload Utility, Bulk Upload REST API & AccountUploader

7 Chapter 7: Master Policy & Platform Management

7.1 Master Policy Framework & Enterprise Compliance Rules 7.2 Platform Architecture, Settings Tree & Platform Duplication 7.3 Platform Policy Overrides, Advanced Settings & Target Tuning

8 Chapter 8: Privileged Session Manager (PSM) Core Architecture

8.1 PSM Architecture, Jump Host Isolation & Service Accounts 8.2 PSM Connection Components (PSM-RDP, PSM-SSH, PSM-Web) 8.3 PSM Universal Connector Framework & Custom Integrations 8.4 Split Workflow: Separating Session Use from Credential Retrieval

9 Chapter 9: PSMP, HTML5 Gateway & Session Security

9.1 PSM for SSH (PSMP) Architecture & Unix Proxy Brokering 9.2 PSM HTML5 Gateway Architecture & Clientless Web Access 9.3 Session Recording, Storage in Recordings Safes & Vault Retention 9.4 CyberArk Remote Access (Vendor PAM): Administering Third-Party Privileged Access

10 Chapter 10: Live Session Auditing, Reporting & Privileged Threat Analytics

10.1 Live Session Monitoring, Shadowing & Active Termination 10.2 Privileged Threat Analytics (PTA) Behavioral Anomaly Detection 10.3 PTA Automated Incident Response & SIEM Integration (CEF/Syslog) 10.4 Vault Reports, Report Authorizations & the Export Vault Data (EVD) Utility

11 Chapter 11: Application Access Manager (AAM) & Secrets Management

11.1 AAM Credential Provider (CP) Architecture & Local Memory Cache 11.2 Central Credential Provider (CCP) & Web Service Integration 11.3 Application Server Credential Provider (ASCP) & Application Authentication (AppID) 11.4 Conjur Secrets Manager & Cloud-Native DevOps Workflows

12 Chapter 12: Directory Integration, Disaster Recovery & Troubleshooting

12.1 Directory Integration: LDAP Mapping, RADIUS MFA & SAML 2.0 SSO 12.2 Disaster Recovery (DR) Vault & PADR Replication Architecture 12.3 Vault Backup Operations with PAReplicate & Safe Recovery 12.4 Diagnostic Procedures, Vault/CPM/PSM Error Codes & System Recovery

11.2 Central Credential Provider (CCP) & Web Service Integration

Key Takeaways Explain This Topic AI

The Central Credential Provider (CCP) delivers an agentless, centralized REST web service hosted on Microsoft IIS, enabling systems to retrieve Vault secrets over standard HTTPS without installing local software.

CCP is specifically designed for serverless architectures (AWS Lambda, Azure Functions), dynamic containers, cloud PaaS services, and locked-down appliances where local agents cannot be deployed.

Requests are formatted as standard HTTP GET calls to /AIMWebService/api/Accounts with query parameters specifying AppID, Safe, and Object (or a general Query), returning responses in JSON or XML format.

Transport and access security is enforced via HTTPS (TLS 1.2/1.3) combined with Client Certificate Authentication (mutual TLS), client IP/subnet restrictions, or Windows Integrated Authentication.

High availability and scalability are achieved by positioning redundant CCP servers behind an enterprise Network Load Balancer (NLB) with stateless round-robin distribution.

Last updated: September 2026

11.2 Central Credential Provider (CCP) & Web Service Integration

Quick Answer: The Central Credential Provider (CCP) is an agentless, centralized REST web service hosted on Microsoft Internet Information Services (IIS) . It allows applications, cloud services, and automation scripts to retrieve Vault credentials over standard HTTPS (port 443) using HTTP GET requests ( /AIMWebService/api/Accounts?AppID=...&Safe=...&Object=... ) returning JSON or XML payloads. CCP is ideal for serverless architectures (AWS Lambda, Azure Functions), containerized microservices, and restricted appliances where installing a local agent is impossible. For enterprise resilience, multiple CCP instances are deployed behind a Network Load Balancer (NLB) .

Agentless Secrets Management: The Central Credential Provider Concept

While the local Credential Provider (CP) delivers maximum performance and offline resilience, modern cloud and enterprise architectures frequently present environments where installing an OS-level agent is impractical or prohibited:

Serverless Compute: Functions like AWS Lambda, Azure Functions, and Google Cloud Functions spin up and terminate within seconds, lacking persistent file systems or background daemon support to run local CP agents.

Elastic Containers: In dynamic Kubernetes clusters scaling rapidly, deploying heavyweight OS agents to every node or container image introduces operational friction and image bloat.

Restricted Appliances & Mainframes: Network firewalls, load balancers, and mainframes run proprietary firmware that prohibits third-party software installation.

Cloud PaaS & SaaS Integrations: Enterprise platforms (Salesforce, ServiceNow, Azure App Services) communicate strictly via outbound web APIs and cannot host local agents.

CyberArk developed the Central Credential Provider (CCP) to address these environments by centralizing the retrieval interface on dedicated web servers.

Architectural Topology & Operational Mechanics

CCP is deployed on Windows Server running Microsoft Internet Information Services (IIS) and the .NET Framework. Architecturally, CCP is a web service application ( AIMWebService ) installed directly on top of a standard local Credential Provider on the same IIS host.

Operational Request Flow

Client Call: The client workload transmits an HTTPS GET request to the CCP web service URL.

IIS Processing & Authentication: IIS terminates the TLS connection, authenticates the client (via client certificate, Windows Integrated Authentication, or client IP address), and forwards parameters to the local provider via in-process .NET SDK calls.

Local Cache Evaluation: The underlying local CP on the IIS host evaluates the query. If the account is present in its local memory or disk cache, it fulfills the query in less than a millisecond without contacting the Digital Vault.

Vault Synchronization: If the account is not cached or requires synchronization, the local CP fetches the credential from the Vault over TCP port 1858.

Response Serialization: AIMWebService serializes the returned credential attributes into a JSON or XML payload and transmits an HTTP 200 response back to the client.

Because the local CP maintains its own cache, CCP minimizes Vault traffic, allowing a small CCP cluster to service thousands of clients.

REST Web Service API Syntax and Parameters

The CCP web service exposes a RESTful endpoint for programmatic secret retrieval:

  • Base Endpoint GET /AIMWebService/api/Accounts?<Parameters> HTTP/1.1
  • Host: ccp.corp.internal
  • Accept: application/json

(Note: An alternative endpoint, /AIMWebService/v1.0/Accounts , is also supported for backwards compatibility).

Query Parameters

  • Parameter Description Mandatory / Optional
  • AppID The registered Application ID defined in the Digital Vault. Mandatory
  • Safe The target Safe containing the requested credential object. Optional (Recommended)
  • Object The specific object name of the account within the Safe. Optional (Recommended)
  • Folder The Safe folder path (defaults to Root ). Optional
  • UserName Queries accounts by the managed account username. Optional
  • Address Queries accounts by target system address/hostname. Optional
  • Query Advanced search query (e.g., Safe=AppSafe;UserName=dbuser;Address=dbhost ). Optional
  • Reason Text justification string recorded in the Vault audit log. Optional

Practical Request Example GET /AIMWebService/api/Accounts?AppID=BillingService&Safe=App_Billing_Safe&Object=OracleDB_Admin HTTP/1.1

  • Host: ccp.corp.internal
  • Accept: application/json
  • JSON Response Payload

Upon successful authentication and authorization, CCP returns an HTTP 200 OK status with a structured JSON response containing the plaintext secret in the Content field along with account metadata: {

  • "Content": "s3cureP@ssw0rd!2026",
  • "PolicyID": "Oracle-Enterprise-DB",
  • "UserName": "svc_pay",
  • "Address": "10.20.30.40",
  • "Safe": "Payments_Prod",
  • "Name": "OracleDB_Admin",
  • "DeviceType": "Database",
  • "CreationDate": 1774051200,
  • "LastModified": 1774094400
  • }
  • Authentication and Transport Security

Because CCP operates as a centralized web service, securing communication and strictly authenticating client requests is essential.

Transport Encryption

All CCP communication must be enforced over HTTPS (TLS 1.2 or TLS 1.3) . Unencrypted HTTP (port 80) should be disabled in IIS to prevent cleartext credential interception on intermediate network segments.

Multi-Tier Authentication Options

CyberArk supports several authentication layers configured in the AppID definition:

Client Certificate Authentication (mTLS): Highest security standard for CCP. The client presents an X.509 certificate during TLS handshake. IIS validates certificate trust, and the Vault matches the certificate's Serial Number , Issuer , or SAN against AppID restrictions.

Client IP Address / Subnet Restriction: The AppID restricts requests to authorized client IP addresses or CIDR blocks (e.g., 10.150.20.0/24 ). Requests originating from unauthorized IPs are rejected with HTTP 401 Unauthorized .

Windows Integrated Authentication (Kerberos / NTLM): Used when calling clients reside within a trusted Active Directory domain, authenticating via domain service accounts.

Anonymous Authentication (Restricted): Permitted only when client certificate or domain authentication is unsupported, provided strict IP address filtering and AppID restrictions are enforced.

High Availability & Load Balancing Architecture

A single CCP server presents a single point of failure (SPOF). High availability and horizontal scalability are achieved by deploying multiple CCP servers behind a Network Load Balancer (NLB) :

Multi-Node Deployment: Deploy at least two independent Windows Server hosts running IIS and CCP across separate availability zones.

Load Balancer Configuration: Configure stateless round-robin or least connections on an enterprise load balancer (e.g., F5 BIG-IP, AWS NLB). Because CCP requests are stateless GET calls, session stickiness is unnecessary.

SSL Handling: If using mTLS, configure SSL Passthrough, or forward certificate details via headers ( X-ARR-ClientCert ) so IIS can inspect them.

Health Monitoring: Monitor CCP health via periodic synthetic GET requests to /AIMWebService/api/Accounts to remove unhealthy nodes automatically.

Comparison: Credential Provider (CP) vs. Central Credential Provider (CCP)

Architectural Attribute Credential Provider (CP) Central Credential Provider (CCP)

Deployment Model Local agent installed on every application host Centralized web service on dedicated IIS nodes

Network Dependency Zero runtime dependency (Runs offline via cache) Dependent on network connectivity to CCP nodes

Retrieval Latency Sub-millisecond (<1 ms via local RAM) 10–30 ms (HTTPS network roundtrip)

Agent Footprint Requires local software install and OS patching Agentless from client perspective (No local agent)

Best For High-throughput apps, DB clusters, offline needs Serverless (Lambda), containers, PaaS, appliances

Protocol Used Outbound TCP 1858 (PrivateArk to Vault) Inbound HTTPS 443 (Client to CCP); TCP 1858 (CCP to Vault)

Offline Availability Complete resilience via encrypted disk cache None on client (Relies on CCP server redundancy)

Loading diagram... Central Credential Provider (CCP) Redundant Load-Balanced Architecture