Service availability and security controls - geo_addressing_1

• Availability model for Production system (where applicable)
  • Contractual obligations for availability and support: Availability Service Level Availability (SLA) 99.9% in a quarter.
• Does the product store or process personally identifiable data (PII), electronic protected health information (ePHI), payment card data, or any other sensitive data?
  • No
• What is the RTO & RPO for systems involved in delivery of service (if applicable)
  • 24 hours, 48 hours
• Is the customer environment separate from other customer systems?
  • Workspaces are logically separated in order to ensure that customer data is kept secure.
• What are the encryption protocols for database, OS, and data in transit?
  • AES256
• What are the backup and data recovery procedures?
  • Disaster recovery is tested at least annually.
• How often are backups performed?
  • At least every 24 hours
• How regularly are your BC or DR plans tested?
  • At least annually
• Do you have service level availabilities (SLAs) and support agreements in place with your hosting provider?
  • Yes.
    • See Service Level Availability (SLAs)
    • See Support handbook
• Have you implemented backup mechanisms to ensure compliance with regulatory, statutory, contractual, or business requirements?
  • Yes. Precisely has implemented backup and recovery policies for all essential systems. The frequency of backups varies depending on the nature and significance of the data and the underlying repositories. Whenever feasible, highly available, resilient, and redundant systems, services, and components are employed to enable automated fail over. Precisely conducts regular, secure tests of backup and recovery processes for both data and supporting systems.

• Do you encrypt tenant data at rest (on disk or storage) within your environment? If yes, to what strength?
  • All customer data held by Precisely is encrypted in transit and at rest. Precisely uses industry-standard encryption algorithms and protocols, such as AES-256, TLS 1.2, and HTTPS, to protect data from unauthorized access, disclosure, or modification.
• What mechanism does Precisely provide for cloud-to-cloud connectivity with DIS APIs?
  • Precisely supports AWS PrivateLink, which enables secure, private connectivity between your cloud environment and Precisely's APIs without exposing traffic to the public internet.
• Why should I use AWS PrivateLink for DIS API integration?
  • AWS PrivateLink ensures that traffic remains within the AWS network, providing enhanced security, compliance, and performance for cloud-to-cloud integrations.
• How is AWS PrivateLink configured for DIS APIs?
  • You create a VPC endpoint in your AWS account that connects to Precisely's API service via PrivateLink. Once set up, your applications route DIS API requests securely through this endpoint.
• Where can I get help with setup?
  • You can follow the AWS PrivateLink documentation for configuration steps, and Precisely's support team can provide guidance tailored to DIS API integration.