If you would like to report a vulnerability or have any security concerns with a Nanoheal product, please contact email@example.com.
Infrastructure and Network Security
Physical Access Control
Nanoheal is hosted on AWS Platform. AWS data centers feature a layered security model as stated in the AWS Security whitepaper, including extensive safeguards such as:
Access logs, activity records, and camera footage are reviewed in case an incident occurs. Data centers are also routinely patrolled by professional security guards who have undergone rigorous background checks and training.”
Nanoheal employees do not have physical access to AWS data centers, servers, network equipment, or storage.
Nanoheal undergoes black box penetration testing, conducted by an independent, third-party tester, as and when major releases are made to the platform. For our enterprise level customers we’re happy to provide the results of their findings and the mitigation we applied.
AWS Cloud Platform undergoes various third-party independent audits on a regular basis and can provide verification of compliance controls for its data centers, infrastructure, and operations. This includes, but is not limited, to SSAE 16-compliant SOC 2 certification and ISO 27001 certification.
Nanoheal is currently in the process of SOC2 implementation and we will update this section as soon we are certified.
Intrustion Detection and Prevention
Unusual network patterns or suspicious behavior are among Nanoheal’s biggest concerns for infrastructure hosting and management. AWS Cloud Platform’s intrusion detection and prevention systems (IDS/IPS) rely on both signature-based security and algorithm-based security to identify traffic patterns that are similar to known attack methods. IDS/IPS involves tightly controlling the size and make-up of the attack surface, employing intelligent detection controls at data entry points, and developing and deploying technologies that automatically remedy dangerous situations, as well as preventing known threats from accessing the system in the first place. Nanoheal does not provide direct access to security event forensics, but does provide access to the engineering and customer support teams during and after any unscheduled downtime.
Business Continuity and Disaster Recovery
Every part of the Nanoheal service uses properly-provisioned, redundant servers (e.g., multiple load balancers, web servers, replica databases) in the case of failure. As part of regular maintenance, servers are taken out of operation without impacting availability.
Nanoheal keeps continuous encrypted backups of data in multiple regions on Amazon Web Services. While never expected, in the case of production data loss(i.e., primary data stores lost), we will restore organizational data from these backups.
In the event of a region-wide outage, Nanoheal will bring up a duplicate environment in a different AWS Cloud Platform region.
Data into servers
All the incoming connections towards our servers are required to be encrypted with industry standard SSL encryption. We do not collect any sensitive information such as Credit Cards, IBAN, SSN in the Nanoheal platform.
Data between our servers
Connections between our servers (i.e. web servers <-> databases) are encrypted via TLS with a AES-256bit encryption method. Secrets such as database password, API secrets are encrypted using the same AES-256bit method.</->
Data out of our servers
Once the request is processed, the response is sent back using the same HTTPs SSL encrypted connection.
Data Security and Privacy
All data in Nanoheal servers is automatically encrypted at rest. AWS Cloud Platform stores and manages data cryptography keys in its redundant and globally distributed Key Management Service. So, if an intruder were ever able to access any of the physical storage devices, the Nanoheal data contained therein would still be impossible to decrypt without the keys, rendering the information a useless jumble of random characters.
Encryption at rest also enables continuity measures like backup and infrastructure management without compromising data security and privacy.
Nanoheal exclusively sends data over HTTPS transport layer security (TLS) encrypted connections for additional security as data transits to and from the application.
Data Retention & Removal
Read more about our data lifecycle policy here.
As mentioned we do not collect any PII information in the Nanoheal Platform. To mitigate accidents and other security risks, Nanoheal offers server-side filtering as a default. Information such as System Serial number can be filtered by not collecting at source through configuration.
All new employees receive onboarding and systems training, including environment and permissions setup, formal software development training (if pertinent), security policies review, company policies review, and corporate values and ethics training.
All engineers review security policies as part of onboarding and are encouraged to review and contribute to policies via internal documentation. Any change to policy affecting the product is communicated as a pull request, such that all engineers can review and contribute before internal publication. Major updates are communicated via email to all employees.
Nanoheal follows the incident handling and response process recommended by SANS, which includes identifying, containing, eradicating, recovering from, communicating, and documenting security events. Nanoheal notifies customers of any data breaches as soon as possible via email and phone call, followed by multiple periodic updates throughout each day addressing progress and impact.
Incident response plan
In case of a security incident it’s best to have a clearly defined plan and responsibilities. Below you will find more details regarding the response plan that Gorgias has in place in the unlikely case of a security breach.
Level 1: Depending on how the incident is reported/discovered we generally have the first level of technical support that is likely to triage/escalate the issue. Normally that role is reserved for whoever is on the level 1 tech support shift at the time.
Level 2: Is the security officer that classifies the impact of the security incident and activates the Security Incident Response team (SIRT)
Level 3: Security officer or CEO is responsible for the communication with the affected parties regarding the details of the breach.
Before escalating the incident to the next level, the person that first finds out about it needs to verify the incident and its initial impact.
Once verified the escalation process should be immediate to level 2 and then level 3 verbally, by phone, email, whatever medium available.
Once escalated the rank/severity of the incident must be determined. Does it affect all customers? A single company? An individual? What type of data was affected if any? Was it encrypted? If so, how?
Analyze all elements of the incident in order to identify all the causes or where a failure occurred including the software, hardware, people, and internal processes.
Based on the result of the investigation, determine what could be done to prevent this attack and what defensive mechanisms failed and take immediate action to re-mediate the cause and improve the future process.