Home
Security

Encryption Standards for Data at Rest and in Transit

## **🔐 FAQ: TLS, Data in Transit, and Data at Rest**

### **What is TLS and how does Dusk FSM use it?**

**TLS (Transport Layer Security)** is a cryptographic protocol that protects data when it moves between your device and Dusk FSM’s servers.
Dusk FSM uses **TLS 1.2 and above** to ensure all communication—including API calls, mobile app traffic, and browser sessions—is fully encrypted and safeguarded against interception or tampering.

This ensures:

* Encrypted communication between client and server
* Protection from eavesdropping and man-in-the-middle attacks
* Verification that users are connecting to the authenticated Dusk FSM service

---

### **How does Dusk FSM protect data in transit?**

All data transferred between Dusk FSM apps, integrations, and backend services is encrypted using **TLS 1.2+** with modern cipher suites.
This includes:

* Job data sent between mobile devices and the platform
* HubSpot, QuickBooks Online, Verizon Connect, and other integration traffic
* Authentication and session information
* File uploads such as forms, attachments, and photos
* Internal microservice communications within the Dusk FSM infrastructure

This ensures no unauthorised party can read or modify the data while it is being transmitted.

---

### **How is data stored (data at rest) protected in Dusk FSM?**

Dusk FSM encrypts all customer data at rest using industry-standard encryption (typically AES-256).
This includes:

* Platform database storage
* File storage (documents, images, attachments)
* Logs, audit trails, and backups
* Customer-specific configuration data

All customer data is hosted on secure **AWS cloud infrastructure**, where encryption at rest ensures protection even if underlying storage were to be accessed improperly.

---

### **Are mobile devices also secured?**

Yes.
Dusk FSM mobile apps follow strict security controls to ensure data is protected on the device:

* Encrypted local storage for offline data
* Secure credential handling using platform-level keychains
* No sensitive data stored unnecessarily
* Automatic session/token expiry
* Optional MDM/MAM support depending on your organisation

---

### **Does Dusk FSM support secure integrations?**

Yes.
All integrations use secure, encrypted communication channels protected by TLS. Depending on the integration, Dusk FSM supports:

* OAuth2 authentication (HubSpot, QuickBooks Online)
* Token-based access
* Signed webhook payloads
* Encrypted data transfer over HTTPS

All external system interactions occur over secure, authenticated channels.

---

### **Where is my data stored?**

Dusk FSM stores customer data on **AWS cloud infrastructure** in secure, region-appropriate environments.
Storage locations are chosen to meet regulatory requirements and customer needs, including:

* Australia
* United States
* Europe

Each region maintains the same security standards, encryption controls, and compliance frameworks.

---

### **Do encrypted backups also follow the same security standards?**

Yes.
Backups are encrypted both:

* **At rest**, using the same AES-256 encryption policies
* **In transit**, when being moved between storage services or during recovery operations

Backup data inherits the same protection as live production data.

---

### **Does Dusk FSM undergo regular security testing?**

Yes.
To maintain a high security standard, Dusk FSM conducts:

* Regular penetration testing
* Vulnerability scanning across infrastructure and code
* Monitoring of TLS configurations and expiration
* Continuous security patching
* Logging and alerting on suspicious activity

Results inform ongoing platform hardening and compliance.

---

### **Is customer data isolated between environments?**

Yes.
Dusk FSM uses logical data separation, access controls, and service-level isolation to ensure:

* Customers cannot access each other’s data
* Internal roles control who can access specific datasets
* Integrated systems only see their authorised data sets

---

Updated on November 18, 2025

Encryption Standards for Data at Rest and in Transit

Need Support?

Error

Delete Article