Share  Email  Print

Cloud Security FAQs

Last edited by kashif at 2017-09-27 14:35:59


Here you will find answers to some Frequently Asked Questions related to Security and Compliance on Aimsfun Application Stack

 

What can I do to protect my instance?

To secure your instances on Aimsfun Application Stack, follow these best practices:

  • Connect securely to your instance. For externally facing applications, it's a good idea to configure your firewalls properly and secure your ports. 
  • Ensure the project firewall is not open to everyone on the internet. Leaving all firewall rules open to 0.0.0/0 will mean that any source on the internet can establish a connection to your instance. Unless you specifically want to make your instance publicly available, a general best practice is to allow access only to your application, and only on the ports your application needs access to. 
  • Use a strong password. Passwords ensure that only authorized people have access to your instance. For information on creating strong passwords, see Creating a strong password. In addition, remember to secure the Gmail account that you use for accessing the AAS Platform Console. 
  • Ensure that all software is up to date. Make sure that the software you have installed is up to date and that there are no known vulnerabilities that could compromise your instance.
  • Monitor project usage closely via the monitoring API to identify abnormal project usage. Aimsfun Application Stack offers centralised logs on dashboard which enables you to collect and store logs from applications and services on the AAS. You can use logging to create log-based metrics for monitoring and alerting on unusual behavior. 

 

What should I do if my Aimsfun Cloud project has been compromised?

As an owner of a project, you are responsible for securing the software installed on your machine. If you feel that your instance has been compromised, the following steps will help with limiting the damage:

  • Stop the instance immediately.
  • Notify impacted users; they might be wondering why your service is down.
  • Identify the source of the vulnerability by analyzing the behavior of your instance and the software you've installed.
  • Ensure that all the software is up to date. Check for any known vulnerabilities in the software installed on your machine and take proactive steps to apply the latest security patches.
  • Adopt additional security measures to ensure that your project is not compromised by a third party and then completely reinstall your project.
  • Follow the guidelines in What can I do to protect my instance? (above) to ensure your project is secure going forward.
  • If you received a warning from Aimsfun Application Stack about suspicious behavior by your project, appeal the warning by going to the Aimsfun Application Stack console and explaining the steps you took to secure the instance.

 

My instance has been compromised. Can you tell me how to fix it?

Unfortunately, we do not have visibility into what is installed on your instance or what software caused the issue. You're responsible for investigating the source of vulnerability and taking steps to mitigate it. If you need any additional support to troubleshoot the issue please refer to the AAS Support page.

 

My instance is secure and I have followed all the guidelines. I still got a warning about suspicious behavior by my instance. What should I do?

There are several reasons why this might happen. Sometimes, a third party application can make your instance vulnerable. It's critical to monitor your instance and ensure that it is secure.

Also, please review the Aimsfun Application Stack Acceptable Use Policy to ensure that your project complies. In extremely rare instances, our algorithms may flag your project's intentional behavior as suspicious behavior originating from a compromised instance. In such cases, you can appeal by going to the Aimsfun Application Stack console and providing a business justification. A member of our team will review your appeal and get back to you within two business days.