Truvera Documentation portal
WebsiteTruvera Workspace
  • Truvera overview
    • Decentralized identity explained
    • Roadmap
    • Subscription plans & billing
  • Solutions
    • Biometric-Bound Credentials
  • Truvera Workspace
    • Create an organization profile (DID)
    • Issue verifiable credentials
      • Filtering, downloading and deleting credentials
    • Verify credentials
    • Create a schema
    • Create a design
    • Team management
      • Inviting a team member
      • Removing a team member
      • Changing team member roles
      • Data retention policies
      • Sub-accounts
    • Revoking credentials
    • Ecosystem Tools
      • Ecosystem set up
      • Ecosystem example
    • Monetizing credentials
      • Setting up monetizable credentials
    • Creating API keys and webhook endpoints
    • Transaction history
    • Custom branded distribution emails
    • Truvera Workspace release notes
      • 2025 Release notes
        • Release notes Q1 2025
      • 2024 Release notes
        • Release Notes February 2024
        • Release Notes March 2024
        • Release Notes April 2024
        • Release Notes May 2024
        • Release Notes June 2024
        • Release Notes July 2024
        • Release Notes August 2024
        • Release Notes September 2024
        • Release Notes October 2024
        • Release notes November 2024
        • Release notes December 2024
  • Truvera API
    • Getting started
    • Webhooks
      • Webhooks API endpoints
    • Sample Postman collections
      • Issue-Store-Verify sample flow
      • Create ecosystems
      • Issue monetizable credentials
      • Create sub-accounts
      • Issue OpenID credentials
    • Truvera Swagger UI
    • DIDs
    • Profiles
    • Credentials
    • Presentations
      • Proof templates
      • Proof requests
      • Other proof endpoints
    • Registries
    • Revocation Status
    • Credential Schemas
    • Jobs
    • Templates
    • Sub-accounts
    • Teams
    • Messaging
    • OpenID
      • OpenID Issuance and Verification Integration Guide
    • iden3comm
    • Ecosystem Tools
      • Trust Registry Integration Guide
      • Creating a Trust Registry
      • Inviting participants
      • Verifiers and Public info
      • Trust Registry Schemas
      • Trust Registry Proof Templates
      • Reports
      • Updating and Deleting Trust Registry
    • Issuing paid credentials (KVAC algorithm integration)
    • Data
    • Verify
    • Keys
    • Schemas
  • System architecture
    • Proposed architecture with Truvera
    • Revocation
    • System scalability
    • Security policies
    • How data is processed and stored
  • Supported standards
    • Interoperability with OpenID
  • Credential wallet
    • Create and manage DIDs in the Truvera Wallet
    • White label wallet
      • Configuration
        • Enabling and Disabling Features
        • Customizing the Styling
        • Configuring for Android Builds
        • Configuring iOS Builds
      • Publishing in App Stores
        • Android Build Testing and Publishing
        • iOS Build Testing and Publishing
    • Wallet SDK
      • Getting started
        • Example Credential
        • Presentation definition
        • Verify credentials
      • Cloud wallet
      • Biometric plugin
      • Ecosystem Tools
    • Download Truvera Wallet
    • Truvera Wallet release notes
      • Release Notes 2025Q1
      • Release Notes 2024Q4
      • Release Notes 2024Q3
        • Release Notes September 2024
        • Release Notes August 2024
        • Release Notes July 2024
      • Release Notes June 2024
      • Release Notes May 2024
      • Release Notes April 2024
  • Open source community
    • Code of Conduct
    • Truvera Credential SDK
    • Blockchain archives
      • DOCK token
        • Migration terms and conditions
  • Support
    • System Status
    • Discord
    • Support services
    • Security policy
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
  1. System architecture

Security policies

Dock Labs strives to follow best practices for information management and system security.

Specific practices include:

  • Strategic Alignment: Aligning security objectives with the overall business strategy to support organizational goals.

  • Leadership Oversight: Managed by a dedicated security manager and subject to regular policy reviews.

  • People Security: Includes confidentiality agreements and mandatory security training. All new hires receive security training as part of on boarding and all team member continue to receive annual security training. This training encompasses key areas such as avoiding phishing attacks and other security best practices, ensuring continuous skill enhancement in security roles.

  • Physical and Remote Work Protocols: Focuses on secure remote work practices, including device security and data protection.

  • Access Control: Enforces the least privilege principle and conducts regular access audits. Our access management policies detail risks associated with system and data access, specifying procedures for granting, monitoring, and revoking access.

  • Robust Password and Data Policies: Ensures strong password use and responsible data management.

  • Change Management: Follows documented procedures for system changes and development.

  • Disaster Recovery: Implements effective backup strategies for business continuity.

  • Incident Response and Preparedness: Developing and maintaining robust incident response plans.

  • Vendor Management: Utilizes proactive monitoring and collaborates with security-conscious vendors.

  • Continuous Policy Enforcement and Updates: Enforces strict adherence to security policies, with annual reviews for relevancy.

  • Risk Management: Identifying, assessing, and mitigating risks to maintain the integrity, confidentiality, and availability of information.

  • Compliance and Legal Requirements: Ensuring adherence to relevant laws, regulations, and industry standards.

  • Documentation Storage: All risk-related documentation, including NDAs, confidentiality agreements, and access management policies, are securely stored in designated, secure repositories, accessible only to authorized personnel. We maintain an audit trail for any changes to these documents.

  • Documented Evidence: Our strategy and security objectives are formally documented in our strategic planning documents and Information Security Policy. These documents detail the specific goals, responsibilities, and procedures that govern our approach to security and overall business strategy. They are reviewed and approved by the management team and are subject to regular updates to reflect evolving business needs and security landscapes.

  • Continuous Improvement: Regularly reviewing and updating security policies and procedures to address emerging threats and changes in the business environment.

We additionally follow specific architectural and coding practices such as:

  • Minimize the storage of Personally Identifiable Information (PII)

  • Encrypt data in transit and at rest

  • Production logs do not contain user data

  • System anomalies are automatically reported to employees so they can be triaged in a timely manner

  • All changes must be reviewed by a team member before deployment

PreviousSystem scalabilityNextHow data is processed and stored

Last updated 5 months ago

Was this helpful?