NMA ZSentry API / Forms
Now we have HIPAA compliant web forms on our website, and fully automate the encryption of form responses back to the office using ZSentry. It was easy for our website developer to integrate with our website.
Already integrated with: Microsoft C#, .Net, Exchange Server, and Office, Java, PHP, HTML web forms, mail clients, and more. For an overview of the ZSentry complete offer, see what's inside.
I need to spend a little time customizing the "skin" and what things say, but I have things working. We think this service will add significant benefits to our application and users.Pricing: Included with one-year or longer user license, for example to use with a web form. For high-volume or special applications, please Contact Us >>
Purpose: Often, enterprises build custom applications using a framework such as Office, .NET, Java, or others, in various servers and hosts, extending functionality. Enterprises also often use functionality already built-in, and customize it for a particular business process. Customized functionality usually involves sensitive data, for the enterprise and customers.
The server-side ZSentry Application Programming Interface (API) allows your custom office application or process, running in hosts or servers, to connect to ZSentry. You can then easily access the ZSentry “bare metal” API for maximum flexibility & performance. For example, an Office or .NET application can be triggered by some event to send a confidential ZSentry message to a group of users, some by secure email and others by secure SMS, and also save it in a secure file. The API works with all ZSentry editions: Desktop, Web, Cloud, and Mobile.
Get to Market Faster: With the ZSentry API, it is easy to send and receive secure data when using custom applications. ZSentry API is also easy to learn, easy to use, hard to misuse, easy to write code that uses it, and sufficiently powerful to satisfy HIPAA, Safe Harbor & other requirements. You can contact a ZSentry Certified Partner or do-it-yourself. We offer developer programs to help integrate the ZSentry API (ZAPI) with your applications, allowing your users and customers to easily comply with privacy regulations, including HIPAA and HITECH Safe Harbor. Please Contact Us for information on available developer programs.
Customer Controlled Operation: To comply with ITAR and financial services regulations, for example, customers may require exclusive control of information. ZSentry API also works with ZSentry Director, which provides local data handling of all plaintext and first-layer security keys.
How it Works: Developers can connect a system to a ZSentry engine for encryption/decryption directly or through a message service or application, using SSL SMTP, automatically. ZSentry can also send the resulting secure emails using its own SMTP server, without requiring SSL, or use another resource as a mail relay with or without SSL.
With the ZSentry API, developers are not limited to use HTTPS with ZSentry App. Applications can also connect using SMTPS (SMTP over SSL, also called implicit SSL) on TCP port 465.
With port 465 there is no ZSentry data exchange without SSL, including the ZSentry Username and Password data. Contrary to the submission port 587 with STARTTLS where the connection changes from non-SSL into SSL, port 465 has SSL-at-connect required. We prefer port 465 because every connection is encrypted from the start, preventing problems such as the SSL bridge attack (a well-known problem also for web browsers).
We tested servers with the dovecot/postfix Debian implementation and, without any errors, against many clients including Outlook, Outlook Express, Windows Mail, Apple Mail, Entourage, and Thunderbird, on Windows XP, Vista, Linux, and Mac OS X.
The ZSentry Client Benefits and also:
Exchange Server: Since 2000, Microsoft Exchange Server extensively uses standards-based SMTP, the same standard used by ZSentry. You can define SMTP connectors in Exchange, both sending and receiving, using SSL and port 465. Exchange SMTP connectors are fully compatible with the ZSentry API. ZSentry can work with Exchange, through Exchange, and directly with clients. You choose which model to use. For example, depending on who you are sending to, you can select to use Exchange as a non-SSL mail relay, to send the message after it is encrypted by ZSentry. Or, you can select to send in SSL to Exchange, which then defines whether or not to encrypt using ZSentry, and how to send it, all based on some policy you defined in Exchange.
Use Now: Request a Support Ticket for information on licensing and using the ZSentry API.
Developer Connection: We have two license programs for developers:
Please Contact Us and let us know which developer program you prefer.
Commercial license, reseller, and distribution terms are independent of the Developer Programs, and can be provided at any time. Click Partner Connect
|Main Technical Notes|