Before submitting your app for approval, ensure the following are resolved:
Phishing prevention mechanisms are in place.
Cross-Site Request Forgery (CSRF) protections are implemented.
Cross-Site Scripting (XSS) is mitigated using appropriate framework/language libraries.
SQL Injection protections are implemented using “Filter Input, Escape Output” techniques.
Additionally:
Ensure all OS and application framework patches are up to date at submission. You must also commit to applying new patches within a commercially reasonable timeframe.
Your external web servers must support TLS 1.1 or higher; TLS 1.2 with AES-256 and SHA-256 is recommended. HTTPS should be enforced for all application traffic.
Implement secure authentication, session management, and access controls.
Secure and HTTPOnly flags on all cookies.Use third-party libraries only from trusted and verifiable sources.
Avoid exposing detailed error messages, stack traces, or logs to users. If you must share crash data, sanitize all private or sensitive information.
Implement event logging for auditing and troubleshooting.
Protect against CSRF by passing a unique, unguessable state parameter with each authorization request. It should not include sensitive data.
Your app must not store, share, or export CustomBooks™ data beyond what is functionally required.
Tokens, OAuth credentials, or customer data must not be shared with any third party without CustomBooks™’s written consent.
Comply with all API rate limits as defined by CustomBooks™.
We reserve the right to test your application via:
Manual architecture reviews.
Feature-based Q&A sessions.
Automated security scanning of your web app and network.
Manual penetration testing for known vulnerabilities.
If you are evaluating CustomBooks™ or want help setting up workflows for your business, explore the product or schedule a conversation with our team.
Already using CustomBooks™? Explore the Knowledge Base or contact support for product help.