We wanted to get back to the group with an update, albeit more than a few hours
later than we would have preferred. Our apologies. Suffice to say, we are very, very busy at present.
After reviewing the documentation surrounding this event, the root cause and resolution are clear. This was a simple
human error, resulting from the misconfiguration of our servers.
As previously disclosed, there were only 2 external connections. Both brief. Further the situation was remedied immediately upon being brought to our attention. Doesn?t excuse the lapse, but on the upside, no Personally Identifiable Information was downloaded by those outside third parties.
That said, we?ve immediately implemented a 3 step check and balance process (which requires sign off of
senior staff member)
before deployment of any hardware that may contain PII. This will ensure that this type of oversight
does not happen again.
Further, our new MMS backend is far better automated, hardened, and scalable, which further reduces/eliminate the risk of these kinds of errors in the future (as well as enabled a host of exciting new features and capabilities).
We are working triple time to get everyone updated and migrated over, but as Aaron has previously posted, this is not a trivial task. We will keep you posted.
//And yes, I did just say that...

Again, on behalf of everyone here at MiOS and Vera, please accept our apologies for this error.
@niharmehta Thanks for the kinds words and welcome. I know you guys have been starving for attention here in the forums and this is
long overdue. You will be seeing a lot of of me, as well as the rest of the staff, in coming weeks and months. Our lack of attention here (however inexcusable) has not been due to lack of action. Quite the opposite actually. More to follow. Soon.