Cryptotaku said:Thanks for your apologies. I understand that the forum moderators and administrators can only do so much and in some cases do have their hands tied. Thank you for accepting responsibility and thanks to the developers for getting various parts of the sites back up.
Now...
As an infosec professional and software engineer, there are a couple of things that are difficult for me to just let slide. I would like to chime in a couple of points, and would greatly appreciate it if some of these critiques and questions can make their way to the "higher-ups."
1.
What was the security vulnerability and what specific data points were compromised? Generally, when administrators force their users to change their passwords, it implies that some or part of the database or filesystem was compromised (as opposed to there existing some sort of minor vulnerability in the web application like XSS or CSFR). The reason I ask this is because I would like to know what other datapoints might have been compromised.
Do your premium members and financial supporters have anything to worry about regarding their credit card / debit card information? If not, can you please elaborate on what the vulnerabilities were and what specific data points were compromised, and ultimately, elaborate on your reasoning to force password resets?
2. As a software engineer who has worked on critical systems that went down, we ALWAYS informed our customers exactly what was wrong, why, and provided daily ETAs. I was disgusted with myself as a developer that our services were down for 48 hours and had trouble sleeping over it.
What is the reasoning for the lack of frequent communication?
3. To continue from point #2, I also find it really difficult to believe that a code review would take multiple months, unless you had one person doing it. I've worked with teams of less than 15 people on projects with tens of thousands of files. Nowadays with continuous integration, regression testing, unit testing, and common security auditing (with tools like tiger and nessus),
can you please elaborate on the processes that were undertaken to solve the problems?
The way that things were put back "piece by piece" make it sound like you are writing a brand new API as you go, contrary to some of the claims that are being made.
4. Last,
what changes is MAL implementing in the future to make sure that:
A) Future security incidents will be handled more professionally
B) More frequent communication with users will be guaranteed
C) More testing and security audits will be routinely conducted
?
I hope I did not come off as rude or disrespectful. As an anime fan, I value this community greatly, and as a security professional and software engineer, found the response from MAL to be extremely unprofessional. I hope that moving forward in the future, things can change for the better. And if you guys need any help or volunteers, please post some volunteer positions or something. I would have loved to have provided any assistance that I could have to get you guys up and going faster.
All the best,
--Cryptotaku