Security Policies

External security

  1. Servers are hosted by AWS (Amazon Web Services)

    1. AWS security

    2. Physically secure AWS data center in Ashburn, VA

    3. Best-in-class continuous network, threat monitoring

    4. VPC (virtual private cloud) separates Niche network from other organizations on AWS

    5. Niche benefits from AWS designing internal systems according to the requirements of the most security-sensitive organizations

    6. We use Amazon GuardDuty for intelligent threat detection powered by machine learning

  2. We use the most recent long-term support (LTS) versions of core app components: Ubuntu, Python, Django

    1. All security patches are automatically applied at least weekly

  3. User passwords are strongly encrypted and salted to prevent brute-force hacking attacks

  4. We use Django, one of the most secure web frameworks

    1. Django prevents multiple attack vectors: SQL injection, XSS, CSRF, clickjacking, host header validation, etc.

    2. Django is frequently updated, and Niche always uses the most recent long-term-support (LTS) version

Internal security

  1. Superuser passwords are regularly rotated, not shared among client sites

  2. Root-level AWS access is limited to Niche CTO

  3. MFA (multi-factor authentication) required for AWS console, Google Workspace access by Niche staff

  4. AWS console access is assigned using the principle of least privilege (need-to-know basis)

  5. User passwords not stored in plaintext, never available to any Niche team members


  1. Client sites exist on isolated database schemas

  2. Each site has its own database user which is restricted to one schema (client)

  3. SSL and HTTPS (encrypted connection) used to encrypt data in transit across the Internet and prevent man-in-the-middle data snooping attacks


  1. All user page loads (requests) are logged for auditing

  2. All server shell logins are logged for auditing

Data backup and recovery

  1. Full nightly database backups for 35 days

    1. All data in Amazon Web Services (AWS) Relational Database Service (RDS) is automatically backed up nightly and retained for 35 days.

    2. In most cases, data can be restored to within a specific five-minute window, minimizing data loss

  2. Optional: Primary data backup to Dropbox (Data Escrow)

    1. Niche Data Escrow is a data backup plan that involves sending a copy of your primary data over the Internet to an off-site host, currently Dropbox. Data Escrow is distinct from AWS RDS backups.

    2. The Dropbox account is set up, owned and managed by the customer. The customer securely authenticates their Niche instance with Dropbox. The Data Escrow process is run nightly but can also be run more frequently. A full backup of select models identified during onboarding is sent securely to Dropbox in CSV format. Data Escrow backups are deleted after 7 days, or longer based on the amount of storage needed.

  3. Recovery Point Objective (RPO): 24 hours

    1. In the event that data needs to be recovered, data recovery will result in the loss of data from no more than 24 hours previous.

  4. Recovery Time Objective (RTO): 4 hours

    1. In the event that data needs to be recovered, data should be recovered, and systems fully operational, after no more than 4 business hours.