Expertly automate your insider list management
Offer secure, anonymous online whistleblowing
Monitor employee trading, effortlessly
Streamline your liability registration
Here we gather answers to help you with questions that you may have related to the "end of life" of InsiderLog 1.0.
If you cannot find the answer to your question(s) below, please reach out to us at email@example.com.
It’s been five years since the introduction of InsiderLog 1.0. We believe that it is now necessary to upgrade the underlying technical infrastructure and application, to ensure a reliable and secure environment for the future.
No, InsiderLog 1.0 has already been patched to close any risk of exploit relating to Log4j. The work with InsiderLog 2.0 started years ago.
The upgrade of the underlying infrastructure and application must be done. However, if you move to our SaaS service before the end-of-life date (31st of March) we will do the migration for you.
If this is your intention, please let us know by responding to our email.
Please download the PDF here for more information.
Yes, all user data and accounts will be preserved.
As every email environment is different, we don’t have the answer to this. Most commonly, the only thing that may need to be considered is that the server IP can change during this process (unless there is an elastic IP that is re-associated).
If you are using our AWS SES service to send emails with InsiderLog through our domain, this is not affected.
If you are not sure of your current setup, the current email settings can be reviewed by a main admin of InsiderLog, at the top of the settings page.
As this migration procedure comes with certain downtime, the best time to do it is when end-users are not expecting to use the service. However, there is no issue per se in proceeding with open insider lists.
Our technical team remains available to support you throughout the process if you have any questions. Please also note that we offer to do the migration procedure for you, as mentioned in the email. However, it is our recommendation that if you don’t feel comfortable doing this, you should not be managing the hosting environment of InsiderLog. Instead, we recommend our SaaS service where we bear the technical responsibility.
The URL of the login page does not change, however, old bookmarks need to be updated by going to the URL manually (e.g. companyname.insiderlog.com). Access credentials remain unchanged for all users.
After the 30th of April, we will not provide any support or updates for InsiderLog 1.0.
The migration is not associated with any costs, even if you get help from the ComplyLog team.
The downtime will depend on several factors but will mostly depend on how much data is stored on your server (the number of insider lists, insiders, and history logs). The expected downtime for most customers is a few hours at most. If you need to understand this in more detail, please coordinate with us and we can help you understand your specific case.
If you perform the migration yourself, it is important that you read the instructions carefully and follow them step-by-step. If something goes wrong during the migration, the server running InsiderLog 1.0 will not be affected (as it is only stopped and not terminated). In the event of an unexpected error, there is always the possibility to roll back and re-do the migration.
Yes. If you have any questions, please send them to firstname.lastname@example.org