CardDAV is a protocol for accessing and synchronising contact data over HTTP. It is commonly paired with CalDAV in groupware platforms, and it uses WebDAV-style methods and properties. Security depends on correctly enforcing who can view, modify, or delegate access to address books and contact collections.
How CardDAV Works
CardDAV is a WebDAV-based protocol for reading, creating, updating, and deleting contact records over HTTP. It gives clients a standard way to synchronise address books across devices and applications, rather than relying on proprietary sync formats. In practice, the protocol sits between the client and a contact store, so access control and collection scoping matter from the start.
Where CardDAV Fits in Groupware and Sync Stacks
CardDAV is commonly deployed alongside CalDAV in collaboration platforms, with one protocol handling contacts and the other handling calendars. That pairing matters because administrators often manage both through the same authentication, authorisation, and account lifecycle controls. A weakness in one service can expose shared user accounts, sessions, or delegated access paths across the wider groupware environment.
CardDAV also reflects a broader WebDAV pattern, where resources are treated as collections with methods and properties that clients can discover and manipulate. This makes interoperability strong, but it also means implementations must correctly enforce namespace boundaries, per-user visibility, and the difference between owning a collection and being allowed to access it.
Security Implications of Contact Data Access
Contact data can seem low sensitivity, but address books often contain personal details, business relationships, internal directories, and metadata that help an attacker map an organisation. If a CardDAV service is overexposed or misconfigured, an adversary may be able to enumerate contacts, tamper with records, or use synchronised data as a reconnaissance source.
Because CardDAV is typically used by many clients over long-lived sessions, compromise can persist beyond a single device. If an attacker gains access to a synced account, they may inherit address book content, cached credentials in the client ecosystem, and any delegated rights tied to that account.
Managing Access, Delegation, and Trust Boundaries
CardDAV implementations need clear rules for who can view, edit, and share address books. Shared collections, delegated calendars, and groupware-wide directory features can blur those boundaries, especially when organisations reuse the same authentication layer for mail, calendar, and contacts. The result is often an authorisation problem rather than a protocol flaw.
That is why the protocol should be treated as a governed access surface, not just a sync endpoint. The safe design question is not only whether a client can connect, but whether the server correctly limits collection discovery, write access, and cross-user delegation for each contact store.
Risk and Threat Considerations
CardDAV risk usually comes from mis-scoped access rather than from the protocol itself. If an attacker or unintended user can reach a contact collection, the exposure can include sensitive relationships, internal naming patterns, and a foothold for social engineering or follow-on account abuse.
Failure mechanism: Weak authorisation, overly broad sharing, or insecure client/session handling allows contact collections to be read or modified by the wrong principal, and synchronisation then propagates the damage to every connected device.
Impact: Organisations can lose confidentiality of personal and business contact data, create integrity issues in shared address books, and increase the blast radius of any account compromise across endpoints and groupware services.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP API Security Top 10 addresses the attack and risk surface, while NIST SP 800-53 Rev 5 sets the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | AC-3 — Access Enforcement | CardDAV depends on enforcing who can view or modify contact collections. |
| IA-2 — Identification and Authentication (Organizational Users) | CardDAV access over HTTP depends on reliable user authentication before sync operations. | |
| AU-2 — Event Logging | CardDAV changes and access attempts should be logged for account-abuse detection and review. | |
| Recommendation — Enforce access decisions on each address book and synchronised contact collection. Require strong authentication before allowing contact sync and collection access. Log CardDAV access and modification events for investigation and accountability. | ||
| OWASP API Security Top 10 | API5 — Broken Function Level Authorization | CardDAV operations like read, update, and share require correct action-level authorization. |
| API1 — Broken Object Level Authorization | Contact collections and address-book items are object-level resources that can be exposed by weak checks. | |
| Recommendation — Verify every CardDAV method and action is authorised for the calling user. Check object-level permissions on each address book and contact record. | ||
Practitioner Guidance
Why practitioners should care: The main operational decision is whether CardDAV access is managed as a simple convenience feature or as a protected business data service. Treat it as the latter whenever address books carry internal, personal, or regulated information.
What to watch for: Review whether client discovery, delegated sharing, and write permissions line up with the actual ownership model of each address book. If users can sync data they should not be able to administer, the protocol is functioning, but the access model is wrong.
Practitioner takeaway: The most common CardDAV failure is not broken synchronisation, it is broken scoping, so validate who can see, change, and delegate each contact collection before broad rollout.
Related resources from NHI Mgmt Group
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 5, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org