Connected systems.
Protected business.
Security for the data, access and workflows connecting Salesforce and ERP.
Security follows
the business process.
Connect the controls around data, identity, actions and operational responsibility.
| Focus | Purpose |
|---|---|
| Protect information | Encryption and data separation help safeguard connected business information. |
| Define access | Roles and authentication help limit access to authorized users and systems. |
| Govern the process | Configured rules, monitoring and exception ownership support controlled execution. |
Security built into
your connected business.
Cloud, network, application and organizational safeguards work together. Deployment-specific settings, interfaces and responsibilities are agreed during implementation.
| Security area | Controls and scope |
|---|---|
| Data protection and separation |
|
| Identity, permissions and account protection |
|
| API authentication and traffic protection |
|
| Cloud, hybrid and private processing options | Duet360 supports cloud and on-premises connections. Where a private runtime is selected, agents can operate behind the corporate firewall and initiate outbound HTTPS communications without cloud-initiated inbound agent connections. Private gateways can keep API processing within a customer-controlled network. Agent topology, proxy requirements, permitted data paths, regional requirements and responsibility for private-agent maintenance are defined for the deployment. Private infrastructure is an architecture option rather than a requirement for every customer. |
| Network and infrastructure security |
|
| Physical safeguards and service resilience |
Recovery objectives, deployment regions, customer-managed backups and service commitments are confirmed in the applicable agreements and solution design. |
| Operational security and secure development |
|
| Privacy, residency and AI governance |
For any connected third-party AI service, confirm its separate data-use terms, permitted tools, accessible records and approval requirements before enabling the workflow. |
| Platform assurance and compliance support | Duet360's underlying platform maintains SOC 1 Type 2 and SOC 2 Type 2 reports, a SOC 3 report, and ISO/IEC 27001:2022 and ISO/IEC 42001:2023 certifications, with cloud security and privacy controls associated with ISO/IEC 27017 and ISO/IEC 27018. Platform resources also address GDPR, CCPA, HIPAA and NZISM requirements. These frameworks have different scopes and obligations. Customer compliance depends on the implementation, organizational practices and applicable agreements. These credentials concern the assessed platform provider and services. They do not represent separate certification or attestation of Duet360 or Endowance Solutions. Supporting evidence and its applicable scope can be reviewed during a security assessment. |
Shared responsibility.
Clear ownership.
Agree who owns access, credentials, monitoring, retention and recovery for your environment.
| Owner | Responsibility |
|---|---|
| Managed platform | Underlying platform security, infrastructure operation and contracted platform services. |
| Endowance | Duet360 configuration, integration delivery, monitoring and support within the agreed scope. |
| Your organization | Source-system permissions, access approvals, customer-managed credentials and infrastructure, data policies and business decisions. |
Security & Trust.
Your questions.
Review the controls and responsibilities for your environment.
Have another question?How is information protected between Salesforce, Duet360 and ERP?
The published platform foundation includes encrypted communications and stored-data protection. Confirm the selected interfaces, runtime, data paths and deployment-specific configuration during the security review.
How are access and integration permissions defined?
Agree organization roles, environment access, service identities and the permissions needed for each operation. Confirm SSO, multifactor authentication and identity-provider responsibilities for the selected deployment.
Can processing use a private runtime or customer-controlled network?
The published architecture includes private runtime and gateway options where selected. Confirm agent placement, outbound connections, proxy requirements and maintenance ownership for your deployment.
What data appears in logs or temporary processing storage?
Design metadata, transaction logs and temporary data have different handling requirements. Agree sensitive-field treatment, permitted log content, retention and authorized access for the workflow.
Who controls approvals for an ERP-changing action?
Define the permitted action, validating rules, required business approval and responsible reviewer. Interface access alone should not be treated as approval for every operational change.
What security commitments should our proposal document?
Record deployment responsibilities, authentication, permitted data paths, logging and retention, support contacts and relevant service commitments. Confirm any required assurance evidence separately; a platform capability is not a certification of every customer deployment.
Build confidence
in every connection.
Review your security requirements with Endowance.
