Security is Salesforce's. So is your data.Kugamon runs inside your org and never holds a copy.

Kugamon is a managed package that has passed the Salesforce AppExchange security review and runs entirely inside your Salesforce org. Customer data is handled by Salesforce — encrypted in transit and at rest, in data centers certified to ISO 27001, SOC 2, FedRAMP, HIPAA and NIST, among others — and Kugamon does not have access to it. Field-level security applies to every transaction record. The certifications below are Salesforce's; the controls are ours.

Control environment

• A dedicated security compliance function implements and monitors Kugamon's security framework and controls.
• The framework consists of policies, procedures and controls that align to ISO 27001, SOC 2, FedRAMP and GDPR and other privacy requirements.
• Kugamon is built on Salesforce, so it uses Salesforce's cloud data centers, which maintain network architecture and data-layer controls that meet the requirements of the most security-sensitive organizations.
• Employees attend security awareness training on hire and annually, and are required to adhere to the Kugamon code of conduct.
• Annual risk assessments address current and emerging risks.
• Change management procedures cover all changes to the organization and to Kugamon's offerings.

Physical security

Kugamon is built and delivered entirely on Salesforce. Salesforce data centers maintain controls at the perimeter, infrastructure and environmental layers, audited regularly against a range of security certifications and standards. Kugamon reviews those certifications annually to confirm the standards are maintained.

The data centers hold several security-related certifications, including ISO 27001, SOC 2, FedRAMP, HIPAA and NIST, and others. These are Salesforce's certifications, published on the Salesforce Trust and Compliance sites, where the latest vulnerability and penetration report summary for Salesforce Services is also available.

Application and network security

• Kugamon follows industry-standard and Salesforce best practices in its application security framework.
• All software releases and new features are reviewed and tested before release, under change management procedures.
• Testing and staging environments are separate from production, and no actual customer data is ever used for testing.
• Automated vulnerability scans run at regular intervals and findings are addressed under a vulnerability management process.
• Automated monitoring, logging and system alerts are in place.
• System access is role-based and least-privilege, including granting and revoking, and all admins and users are formally reviewed quarterly.

In practice, a release reaches customers the same way each month: pushed to sandboxes first, then to production, so an administrator can verify it against their own configuration. The release history page shows the cadence.

Salesforce security requirements

• Kugamon is built entirely within Salesforce and is therefore subject to Salesforce's security policy requirements, which any application must demonstrate to be listed on the AppExchange.
• Kugamon adheres to AppExchange security requirements, which require secure-coding best practices.
• Kugamon is subject to Salesforce security reviews, which examine code quality and code security. Kugamon is a managed package, and passing that review is a condition of its AppExchange listing.

The governing documentation is Salesforce's ISVforce Guide and the AppExchange security requirements checklist, linked in the sources.

Security inside your org

Because every Kugamon record is a Salesforce record, your org's security model is Kugamon's security model:

• Object and field-level security — profiles, permission sets and field-level security apply to Quotes, Orders, Invoices, Payments, Contracts and Subscriptions as they do to any object, and Kugamon enforces field-level security on every transaction record.
• Sharing and visibility — record ownership, role hierarchy and sharing rules govern who sees which transactions.
• Restricted records — a Quote, Order or Invoice can be marked Restricted, which disables emailing and online preview and watermarks the PDF, so records not approved for external viewing cannot leave the org by accident.
• Customer-facing pages — the online Quote, Order, Invoice and Payment pages run through a Salesforce Site guest user to which the administrator assigns the Kugamon Site Guest User permission set, so what a customer can reach is governed by that permission set and Salesforce's guest-user rules.
• Payments — card and ACH transactions are processed by the connected gateway (Stripe, Authorize.Net, PayPal or eWay); the Payment record stores the processor's transaction ID, card type and last four digits. Saving a payment method for reuse is off by default and enabled by Kugamon Support on request.

Encryption

• Customer data is handled by Salesforce, which means it is encrypted in transit and at rest.
• Kugamon does not have access to customer data.

Salesforce publishes its first-party storage encryption summary on its compliance site.

Availability

• Service delivery is handled by Salesforce, which performs regular backups of data; backup testing is performed annually.
• Kugamon's incident response and disaster recovery policies and procedures, and their testing and team training, are performed annually.

Questions about any of the above go to support@kugamon.com. The contractual terms are in the Master Subscription Agreement and the privacy policy.