Kanmon's SOC 2 compliance

We are pleased to announce that Kanmon is now SOC 2 Type I compliant.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

As a leading provider of embedded commercial financing infrastructure for B2B software platforms, Kanmon is committed to maintaining the highest levels of information security. The platforms we work with and their customers trust us with valuable business data, which is why we make compliance a top priority in our product development, processes, and teams.

We are pleased to announce that Kanmon is now SOC 2 Type I compliant. This means that we have successfully passed an independent audit and meet top industry standards for software compliance and security best practices across our organization. Our customers can trust that we are committed to protecting their data.

Our System and Process

Obtaining SOC 2 Type I compliance is a rigorous process that audits against five key criteria:

  • Security: This criteria tests whether customer information is protected from unauthorized access at all times, and validates the systems in place to handle that information.

  • Availability: This criteria deals with the availability of our systems, including system performance, downtime, and incident handling.

  • Confidentiality: This criteria involves the handling and security of data deemed confidential.

  • Privacy: This criteria deals with the secure collection, handling, and storage of personal information.

  • Processing: This criteria addresses the integrity of our data processing, including error detection and resolution, as well as data storage and maintenance.

Our systems were reviewed in their entirety, including the architecture and data flow. This included how data is managed and stored, as well as any third-party vendors or services we use. The review included documentation, testing, and certain recommended revisions to ensure security.

Documentation of all policies related to security and privacy was also a key part of the examination. This meant defining a series of policies across a number of compliance categories, as well as providing evidence that these policies are enforced.

Our Commitment

At Kanmon, we are committed to protecting our customers’ data and privacy. Our customers can trust that their data is safe and secure with us, and that our systems are running smoothly.

“Achieving SOC 2 compliance is a high priority part of Kanmon’s commitment to protecting our partners’ and their customers’ data,” said Rohit Sharma, Co-Founder and COO. “We will continue to work hard to maintain these controls and improve our security posture.”

We hope that this latest certification helps to demonstrate our commitment to security, compliance and privacy at Kanmon. As we work to continuously monitor our controls over time, please don’t hesitate to reach out with any questions. 

If you would like to learn more about this certification, or how we work with industry-specific platforms to offer working capital solutions to their business customers, please feel free to contact us at info@kanmonhq.com

What’s a Rich Text element?

The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.

Static and dynamic content editing

A rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!

How to customize formatting for each rich text

Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.

Introduction

Mi tincidunt elit, id quisque ligula ac diam, amet. Vel etiam suspendisse morbi eleifend faucibus eget vestibulum felis. Dictum quis montes, sit sit. Tellus aliquam enim urna, etiam. Mauris posuere vulputate arcu amet, vitae nisi, tellus tincidunt. At feugiat sapien varius id.

Eget quis mi enim, leo lacinia pharetra, semper. Eget in volutpat mollis at volutpat lectus velit, sed auctor. Porttitor fames arcu quis fusce augue enim. Quis at habitant diam at. Suscipit tristique risus, at donec. In turpis vel et quam imperdiet. Ipsum molestie aliquet sodales id est ac volutpat.

Image caption goes here
Dolor enim eu tortor urna sed duis nulla. Aliquam vestibulum, nulla odio nisl vitae. In aliquet pellentesque aenean hac vestibulum turpis mi bibendum diam. Tempor integer aliquam in vitae malesuada fringilla.

Elit nisi in eleifend sed nisi. Pulvinar at orci, proin imperdiet commodo consectetur convallis risus. Sed condimentum enim dignissim adipiscing faucibus consequat, urna. Viverra purus et erat auctor aliquam. Risus, volutpat vulputate posuere purus sit congue convallis aliquet. Arcu id augue ut feugiat donec porttitor neque. Mauris, neque ultricies eu vestibulum, bibendum quam lorem id. Dolor lacus, eget nunc lectus in tellus, pharetra, porttitor.

"Ipsum sit mattis nulla quam nulla. Gravida id gravida ac enim mauris id. Non pellentesque congue eget consectetur turpis. Sapien, dictum molestie sem tempor. Diam elit, orci, tincidunt aenean tempus."

Tristique odio senectus nam posuere ornare leo metus, ultricies. Blandit duis ultricies vulputate morbi feugiat cras placerat elit. Aliquam tellus lorem sed ac. Montes, sed mattis pellentesque suscipit accumsan. Cursus viverra aenean magna risus elementum faucibus molestie pellentesque. Arcu ultricies sed mauris vestibulum.

Conclusion

Morbi sed imperdiet in ipsum, adipiscing elit dui lectus. Tellus id scelerisque est ultricies ultricies. Duis est sit sed leo nisl, blandit elit sagittis. Quisque tristique consequat quam sed. Nisl at scelerisque amet nulla purus habitasse.

Nunc sed faucibus bibendum feugiat sed interdum. Ipsum egestas condimentum mi massa. In tincidunt pharetra consectetur sed duis facilisis metus. Etiam egestas in nec sed et. Quis lobortis at sit dictum eget nibh tortor commodo cursus.

Odio felis sagittis, morbi feugiat tortor vitae feugiat fusce aliquet. Nam elementum urna nisi aliquet erat dolor enim. Ornare id morbi eget ipsum. Aliquam senectus neque ut id eget consectetur dictum. Donec posuere pharetra odio consequat scelerisque et, nunc tortor.
Nulla adipiscing erat a erat. Condimentum lorem posuere gravida enim posuere cursus diam.