Versions Compared

Old Version 5

changes.mady.by.user Parsa Shiva

Saved on

compared with

New Version 6

changes.mady.by.user Parsa Shiva

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

1. Data Storage

Description:
Contract data is metadata are stored in multiple locations to ensure data integrity, accessibility, and compliance with security standardsour database, while contract content is stored as Atlassian issue/page attachments.

  • Internal Database:

    • Content Stored:

      • Contract configuration metadata (e.g., fields, rules, and settingssigners' and watchers' PII).

      • Audit logs for all contract interactions and updates.

      • Access keys and signer-specific metadata.

  • Atlassian DatabaseAttachments:

    • Content Stored:

      • Contract content in HTML format for editing.

      • Generated contract PDFs for final signature signing processing.

...

2. Data Processing

...

  • Steps:

    1. Fetch contract metadata from the database (content hash, signer data, attachments).

    2. Verify the contract's HTML content for consistency and integrity.

    3. Embed signer details (signature, field values) into the contract.

    4. Store updated contract data ( HTML , metadata) back into the systemcontent and metadata as attachments.

...

3. Signature Certification

...

  • Processes:

    1. HSM (Hardware Security Module):

      • Manages private key storage for secure signing operations.

      • Ensures that private keys remain protected during signature generationthe security of private keys by strictly confining them within its hardware boundaries.

    2. AATL (Adobe Approved Trust List):

      • Guarantees that signatures use trusted certificate chains validated by Adobe.

      • Ensures compatibility and trust in Adobe Acrobat and related software.

    3. LTV (Long-Term Validation):

      • Appends timestamping and validation information to ensure long-term validity of digital signatures.

      • Uses a trusted timestamping authority (e.g., Digicert TSA).

...

  1. Receive signature data, including the contract ID, signer ID, and OTP.

  2. Fetch associated metadata (e.g., contract hash, attachment IDs) from the database.

  3. Verify signer credentials and contract signability.

  4. Embed user signature and field values digital signature into HTML content.

  5. Digitally sign the contract PDF using Google Cloud HSM.

  6. Timestamp the PDF using a trusted timestamping authority.

  7. Append LTV information for future validation.Store updated contract files and metadata in the database.

  8. Notify stakeholders via webhook and email about signing completion.