Defense-in-depth technical controls, encryption standards, and responsible disclosure
Connected email passwords, OAuth tokens, and sensitive integration keys are protected using AES-256-GCM authenticated encryption before database storage.
Session tokens are isolated from browser JavaScript using strictly scoped HttpOnly cookies and verified using cryptographic CSRF validation tokens.
Credentials are only decrypted in transient volatile memory during active outbound dispatch cycles and purged immediately upon socket completion.
Sales Morgan applies authenticated symmetric cryptography to protect connected credentials and tokens:
To protect customer accounts against Cross-Site Scripting (XSS) and Cross-Site Request Forgery (CSRF):
HttpOnly, Secure, and SameSite=Lax attributes. Authentication tokens cannot be read or stolen by third-party browser scripts.Sales Morgan connects with external platforms exclusively through official authentication dialogs (Meta Graph API and LinkedIn OpenID Connect). We do not store raw social passwords, inject browser cookies, or employ unofficial scraping bots. Inbound webhook events and profile tokens are cryptographically verified in real time.
Sales Morgan maintains a documented Security Incident Response Plan. While no software platform can promise absolute invulnerability, we maintain continuous monitoring, defense-in-depth controls, and structured response procedures:
We welcome reports from independent security researchers and ethical security professionals. If you believe you have discovered a vulnerability in our application, API, or infrastructure, please follow our responsible disclosure guidelines: