Vai al contenuto principale
BlogLinodeUn vecchio sistema e una squadra SWAT

Un vecchio sistema e una squadra SWAT


Questo è ciò che i dipendenti di Linode, insieme ai bravi uomini e donne del dipartimento di polizia di Galloway, hanno dovuto affrontare questo pomeriggio: la squadra SWAT ha fatto irruzione nell'ufficio di Linode, costringendo tutti a uscire per circa un'ora mentre eseguivano una perlustrazione dell'edificio stanza per stanza, con tanto di cane che fiutava gli esplosivi (che era molto felice). Avevano ricevuto una falsa segnalazione che li ha spinti a reagire in questo modo - ed è il loro lavoro, dopo tutto, rispondere alle segnalazioni, anche se si rivelano essere una bufala. Sono stati fantastici e li ringrazio.

Non a caso, più o meno nello stesso periodo siamo venuti a conoscenza del fatto che un vecchio server personale ha avuto accesso a un database utilizzando le vecchie credenziali del forum ottenute durante l'incidente dell'anno scorso. Questo server non è sotto l'ombrello del nostro team di sicurezza perché non svolge alcun ruolo nell'infrastruttura Linode. Sfortunatamente, il database del forum phpBB è stato ripristinato dal 2010-03-03. Gli utenti del forum che esistevano a quell'epoca sono stati informati di un problema di sicurezza. Gli utenti del forum che esistevano a quel tempo e che non hanno cambiato le loro credenziali da allora sono stati revocati e dovranno reimpostarle. Ci dispiace che ciò sia accaduto e ci scusiamo per la svista. Discuteremo nuove politiche di sicurezza per affrontare scenari come questo.

Per quanto riguarda la sicurezza, l'anno scorso abbiamo interrotto tutti gli altri sviluppi e ci siamo concentrati solo sulla sicurezza per oltre sei mesi. Abbiamo fatto tutto quello che ci veniva in mente, dalla riduzione significativa della nostra impronta su Internet, alla definizione, al test o al miglioramento delle pratiche e delle politiche per il futuro, ai test di penetrazione di terze parti. Abbiamo fatto tutto questo finché non abbiamo esaurito le cose da sistemare e le idee da perseguire, e il nostro team di sicurezza continua a valutare in modo proattivo la nostra infrastruttura e i nostri servizi. Si è trattato di uno sforzo monumentale e di una storia che merita di essere raccontata, ma questi sforzi e i loro risultati sono oggetto di un post a sé stante. Restate sintonizzati.

Sappiamo quanto sia importante la trasparenza e che in passato avremmo dovuto fare un lavoro migliore al riguardo, ebbene... questa è la storia.

Come sempre, per qualsiasi domanda non esitate a contattarci.


Christopher S. Aker
Fondatore e amministratore delegato di Linode

Commenti (26)

  1. Author Photo

    Heh, and they posed and all. Oh well, stuff happens.

  2. Author Photo

    Basic rule of computer security – there is no such thing as a “low risk” machine. In corporate environments (eg banks) all desktops, all laptops, all services (even DEV machines) need to be secure. If it’s on the network then it’s a risk and needs security. If it was on the network and isn’t any more then it needs proper decomminissioning (disk wipe, etc).

    Similarly backups; any backup tape needs security; any machine that has a backup restored to it needs security.

    BYOD means segmented networks and virtual desktops (never ever plug a BYOD device into your main WAN/LAN).

    And so on. Basically every single bit of data needs to be secured.

    You can’t play games. Every single one of your machines *MUST* be under the remit of your security team.

    Security is hard. Security is expensive. But you need to do it.

  3. Author Photo

    Sounds like a great goal guys, exactly what I’m hoping you’ll improve!

  4. Author Photo

    Increased security is great, but where’s your transparency report? I want to know about the the people who breach your systems in the courts in addition to through the firewall.

  5. Author Photo

    This is the most confusing article I’ve ever read. Looks like somebody swatted you guys, and you seem to be happy about it

  6. Author Photo

    “Basic rule of computer security – there is no such thing as a “low risk” machine.”

    The rallying cry of amateurs everywhere.

    You have to prioritize, or you’ll get nothing done. At most, you might say that the server should have been under the remit of the security team, but the end result may have legitimately been the same: “this machine is not a major priority due to the low potential impact of an attack against it”.

  7. Author Photo

    How were the passwords hashed? From what I can tell from the phpBB sources, it’s using md5.

    If the passwords taken were md5 hashed, then they can be trivially unmasked, and this is a major breach. Burying it in the middle of an unrelated article is a very strange thing to do.

  8. Author Photo

    “The rallying cry of amateurs everywhere.”

    *gigglefit*. I _am_ a security professional working in a bank.

    Data needs to be classified. Even the lowest classification of data isn’t allowed out of the bank. Production data _never_ goes to UAT or DEV. You segment and firewall. Restore prod data to another machine and that server is now classified as PROD.

    Servers with customer data on it (even if it’s just a forum) is considered holding PII data and is under higher scrutinity.

    Every single machine is behind a firewall. BYOD _is_ on a segmented network.

    Every single server (approx 100,000 servers) has centralised monitoring and controls. Every single desktop (approx 250,000) is locked down. You plug your own device in… disciplinary action.

    Yes, we’re a bank; we have to take this shit seriously.

    I’ve been doing this for 20 years; the one thing I ain’t is an “amateur”.

    All that said; yes you need to prioritise; this is “high risk”, this is “medium risk”, this is “low risk”; “this is a risk we accept because the probability is low (firewalled; controlled access; etc) and the consequences are minor (developers can’t work for a day)”, “this is a risk we’ll fix in 3 months (higher chance of it happening, no customer impact)”, “this is a risk we’ll fix tomorrow (shit, panic!)”.

    BUT caker wrote “We did this until we ran out of things to fix and ran out of ideas to pursue”. I gave a tonne more ideas to pursue. Security never stops. If you run out of ideas then you’re not doing your job as a security professional because there are _always_ more things to do.

  9. Author Photo

    >This server is not under the umbrella of our security team because this server plays no role in Linode infrastructure. Unfortunately, it did have a restore of the phpBB forum database on it from 2010-03-03.

    So is it normal that Linode takes database dumps and puts them on servers outside of the Linode infrastructure?

    If I worked at Amazon and took a database dump of one of their systems and loaded it up on a server outside of their control, I’m pretty sure I’d be fired.

  10. Author Photo

    This has got to be the dopiest most out of shape looking SWAT team I have ever seen. Which is saying something since ever rinky dink cop dept has one now.

  11. Author Photo

    Thank you for allowing us to place our backdoors into your enterprise systems. –NSA

  12. Author Photo

    So the SWAT had access to all customer data and servers? Yeah … but I guess I cancel my Linode account.

  13. Author Photo

    “You have to prioritize, or you’ll get nothing done.”

    Well said @cwillu!

    Banks are different in that they have so much money efficiency is not an issue. It’s not a business model you could copy in any another line of business. Least of all the innovative business of cloud servers 🙂

  14. Author Photo

    You focused on security and yet the 2-factor authentication for the Linode app doesn’t include it. That’s basic stuff that was either overlooked or not addressed…

  15. Securty policy – blah ( fall)

    When you do security there are no such term as “low risk”. Example – Somebody install phpBB and Linode just got two step attack. Get out everyone by falser report Attack old forum – get it. So, questions are: does Linode employes doesn’t

  16. Author Photo

    I know you guys are relieved that the SWAT visit turned out to be a false alarm, but the alarm your users feel about the data breach is very real.

    I’m concerned about the flip and casual nature of your dismissal of the database that was exposed, as well as the fact that it was exposed at all. The “oh, BTW, this happened too, but it’s not a big deal” attitude IS a big deal to us.

    I’m sure you understand that we have to have confidence in you the same way that you have to have confidence in your service providers. How comfortable would you feel if one of the service providers you absolutely depend on posted about a data breach in this fashion?

    If your attitude toward security mirrors the overall tone of this announcement then we all have something to worry about.


  17. Author Photo

    Call me Paranoid IT guy but…

    Check every keyboard and keyboard cable for keyloggers. Check the insides of every computer for anything that should not be there. Check every network port in the wall, under the floor, and in the ceiling for signs that anything has been put in there. Check every inch of cable you can physically get access to. Then reflash the BIOS on every machine they could have had physical access to. That includes printers, switches, and anything else that has an IP stack.

    The NSA has shown they are willing to go to extreme lengths to steal data and Linode holds quite a lot of foreign data.

  18. Author Photo

    Someone sends a false report in to generate a SWAT response and people seem OK with that?

    Call me crazy but I’m far more concerned with the casual attitude taken toward heavy handed police responses than I am about some ancient server sitting in a corner with an ancient database on it.

  19. Author Photo

    Why mix up the two unrelated (yet both serious) incidents in this post? Looks like you’re trying to hide the DB server snafu by posting SWAT team pix.

  20. Author Photo

    I’m just going to be another voice that echoes those before me.

    This rather obvious playing down of a data breach is very worrying. Linode’s history regarding security is not exactly good, add on to that a flippish attitude toward a security breach, and you have me seriously doubting my choice of provider.

    I am thoroughly disappointed in Linode.

  21. Author Photo

    Although it’s entirely possible there’s a hardware keylogger somewhere in Linode’s offices right now, I seriously doubt it.

  22. Author Photo

    I can’t imagine what they were going to use the high powered rifles for.

    Were they going to shoot the bomb when they found it?

  23. Author Photo

    Does that pooch eat penguins?

  24. Author Photo

    Was it the green car they drove to check you guys out.?

  25. Author Photo

    Thanks for being transparent. Means a lot

  26. Author Photo

    So, sounds like everyone here is an expert at something…

    Sorry, not to minimize your credentials, but I’m guessing that the people who know best how to secure the Linode systems are the people who work with them daily. A bank security specialist and the NSA security gurus probably have different tasks (which have almost nothing to do with securing Linode), but what kills me – is the morons who are criticizing the police officers who had nothing to do with the security breach at all.

    @Samson: “heavy handed” police response? Wow – you must have known it was a false report before the police even did – so you can sit back in your chair like you know what you’re talking about when it comes to policing all, and not actually providing any solutions to your perceived concerns. Way to go champ.

    @Freedom: Your comment is just way under-supported with actual fact. Love the expert critique you must have on the swat teams though. Sounds like you are in one to know these details. Actually, the photo does not even look like a swat team to me (class A pants, no swat identifiers, etc), probably just a bunch of cops who happen to be on-duty at the time of the call, some who may be on a swat team also.

    @Linode: Thanks for the information. Most Internet companies would not have even bothered to track down a security problem like this or disclose it to their customers. I think this response was appropriate and justified. Keep up the good work! We all know Linode is a highly visible target.

    -My “credentials” include 21 years of IT Security at a multinational ISP, 9 years on a SWAT team.

Lascia una risposta

Il vostro indirizzo e-mail non sarà pubblicato. I campi obbligatori sono contrassegnati da *