Security FAQ

How are job instances protected from unauthorized access?

Instances are secured using security groups and firewalls. They are only accessible via SSH from the PERIAN job platform for workload deployment and monitoring. The PERIAN platform exclusively uses SSH keys for authentication, with no password-based access permitted. No other instances, whether within the same account, VPC, or the public internet, are permitted to connect to the job instance.

Can multiple jobs from the same or different organizations share a single instance?

No, each instance is dedicated to a single job and is terminated once the job container completes.

Does each organization/job have its own VPC?

No. Organizations that use our shared accounts (rather than Bring Your Own Account) share VPCs with other organizations. However, communication within the VPC is still blocked by security groups and firewalls.

Does PERIAN offer encryption at rest and in transit? What encryption mechanisms are used?

PERIAN Job Platform offers serverless compute resources. Communication with user data sources is encrypted with SSL/TLS. Since PERIAN does not manage the user storage yet, it’s up to the user to add additional layers of encryption at rest.

What makes PERIAN GDPR compliant?

All PERIAN services are hosted on GDPR-compliant servers in the EU and adhere strictly to full compliance and privacy policies (incl. AVV/DPA). The team conducts regular privacy assessments to uphold and enhance privacy standards. PERIAN reviews all portfolio cloud providers for compliance and only works with tier 3 and tier 4 cloud providers. Customers can always control and see where their data is stored and processed.

Reporting issues or concerns

If you have any issues or concerns, please email [email protected]. A member of the team will respond within one business day.