Parties
Identify each party by legal name, role, and contact for security notices; assign primary and escalation contacts for credential issues.
This addendum reduces operational and security risk by documenting responsibility for credential issuance, access limits, and retention. It creates an auditable record useful for incident response, vendor management, and regulatory reviews such as HIPAA or GLBA compliance.
Who completes the addendum depends on the relationship: internal teams, vendors, or contracted service providers usually supply credential details.
The document is also used by legal, security, and IT to record obligations and support audits.
Identify each party by legal name, role, and contact for security notices; assign primary and escalation contacts for credential issues.
List each credential type, identifier, and scope (account, system, or API) while avoiding posting secrets in publicly viewable fields.
Specify permitted uses, systems accessible with the credential, and any prohibited activities such as exporting data or re-sharing credentials.
Require controls like encryption at rest/in transit, MFA, credential masking, minimum password entropy, and approved vaulting solutions.
Define issuance date, expiration or review dates, rotation schedule, and procedures for suspension, revocation, or emergency access.
State audit logging expectations, retention period for credential records, and the responsible custodian for preserving evidence.
| Field | Configuration |
|---|---|
| Authentication Method | Require SMS code or SSO verification before revealing any sensitive details to signers. |
| Field Validation | Mask secret fields and accept only non-secret identifiers in the visible document. |
| Role-Based Access | Limit who can view or edit credential fields by role (IT admin, security officer, legal). |
| Audit Settings | Enable full audit trail capture (IP, timestamp, action) and record retention for compliance reviews. |
Use platforms that preserve audit trails, support masked fields, and integrate with secure vaults for secrets.
Date the addendum becomes operative; starts obligations.
When credentials are issued to the designated user or system.
Date when credentials expire automatically or require rotation.
Planned rotation date per schedule (e.g., every 90 days).
Scheduled review date for records and audit logs.
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial | Varies by plan | Varies by plan | Varies by plan | Varies by plan |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
| Envelope Cap | No cap | 100 envelopes/user/year | Varies by plan | Varies by plan | Varies by plan |