text stringlengths 0 2.35k |
|---|
**Kris Brandow:** And of course, they're using all the shiny things with Kubernetes, so that's using Istio. No one actually knows how any of this works. It's just like, "Oh, this is what we're supposed to be using." So we have this big ol' cluster, and it's running, and our DevOps people are pulling their hair, because... |
And then months and months later, someone stumbles across this one auth policy that has no labels, and no access rules, which in Istio language means that it applies to literally everything, and allows all traffic in. So this one policy had just opened our entire API, including the public API, to the entire internet, f... |
I think the total amount of time that the door was just open was about nine months, and to the knowledge that people had, nothing bad happened... But yeah, it was quite horrifying. |
**Johnny Boursiquot:** That is still a security incident requiring disclosure, I'm afraid. |
**Kris Brandow:** Yeah. |
**Dee Kitchen:** I know. I'm just like, "Is this disclosure?" \[laughter\] |
**Kris Brandow:** Yeah, it was like, "Oh... Oh, no." It taught me a lesson that like when I see funky things, I should probably bring them up a little bit. Like, "No, no, that policy is there", and that policy definitely doesn't work. And some of the broken things were like some YAML white spacing thing, where it's lik... |
**Mat Ryer:** Yeah, I think that also is a bit of a lesson, is if there are bits of code and you're like, "No, yeah, but that doesn't do anything now. Like, that used to be doing something and now it doesn't." It's like, either take it out... If it's really not doing something, get rid of it." |
**Johnny Boursiquot:** Prove it. |
**Mat Ryer:** Exactly. It probably is doing something... And if it isn't, maybe it should be, like in your case, Kris. |
**Kris Brandow:** Yeah. |
**Mat Ryer:** Spoopy... |
**Natalie Pistunovich:** The zombie apocalypse. |
**Mat Ryer:** Yeah. |
**Johnny Boursiquot:** ...will be caused by Istio... \[laughter\] |
**Natalie Pistunovich:** Zombie code just haunting us. |
**Dee Kitchen:** I'm never sure what's worse than those things... Like, the insecure environment, where it just like nothing applies, or the extremely secure environment. I've seen somewhere, they've been really locked down, and like everything; you've got an IP firewall rule for everything, and you're like, "I have to... |
And what we realized - the debugging for this went wild; it went really low. And we were down at Wireshark and we're watching what's going on, and we're watching what's going on inside the kernel, but we were turning on contract connection tracking. And this is in TCP, it's got little tables, state tables in there to k... |
\[46:16\] So we were taking existing connections and then just randomly dropping them every time we flipped these things... But we could never observe it, and we were just there the whole time, just going "We've lost it again. There goes the connection." |
And it took us weeks of just poking around, going "What's going on? I can't see it. Ghost in the machine." Yeah, too secure is a problem. Honestly. |
**Mat Ryer:** Well, in that spirit, Dee, what's your pin number? Just give us three of the numbers. Let's play mastermind. |
**Dee Kitchen:** It's just like -- what was it, Spaceballs? 1234... \[laughter\] |
**Mat Ryer:** Yeah. No one's gonna suspect that, I think. No one's going to try that, are they? |
**Kris Brandow:** 0000... |
**Dee Kitchen:** Does it allow you? I don't think systems allow you to do that. |
**Mat Ryer:** Why? |
**Dee Kitchen:** I don't know. I'm gonna try and change my pin now... \[laughter\] |
**Mat Ryer:** Oh yeah, I don't know... Maybe because it's too easy. But I don't know. Any other horror stories before we throw a -- what do you put on fire, water? You don't do that, do you? You just let it die out on its own. No, we've got to be responsible. How are we going to sort this fire out? |
**Johnny Boursiquot:** By throwing water in the electrical equipment? |
**Kris Brandow:** Foam. We'll use foam. |
**Dee Kitchen:** Turn it off. |
**Kris Brandow:** We'll use found close Slack. Yeah, close Slack... |
**Mat Ryer:** Yeah, and the fire will die down. So before we put the fire out, has anyone got any other final horror stories? |
**Dee Kitchen:** Well, you know a few of mine... Any one you want to hear? |
**Mat Ryer:** What, do you mean in real life? \[laughter\] |
**Dee Kitchen:** I wrote one down, which actually I wrote in advance, about doing a SQL statement and accidentally double -- putting in the semicolon after the from table. So an update. So the WHERE statement didn't apply... And that was to a production system... |
**Mat Ryer:** So what was the effect of that then? So normally, you would be updating something and specifying the WHERE, which will limit what gets changed, right? |
**Dee Kitchen:** Yeah, exactly. I tweeted this when you actually asked about it, and I think no one really appreciated what it does and how it happened. But I executed the query; I was just tidying up some debt that was leftover, and it should have been really trivial... And I practiced it, and then I copy and pasted i... |
**Kris Brandow:** Oh, God... |
**Dee Kitchen:** And the machine was very fast; faster than I was at finding Ctrl+Z. |
**Mat Ryer:** Oh, no...! |
**Johnny Boursiquot:** And that's why you work inside of transaction blocks, kids. \[laughs\] |
**Dee Kitchen:** That's why that's advisable, but it was not what I was doing that day. The real mess though was actually sort of going "How can we restore this when our database backup was like 12 hours ago, and there's 12 hours of changes in other tables since then?" |
**Johnny Boursiquot:** Ouch... |
**Dee Kitchen:** So you're not going to sort of do anything there. So it's a pull the old sort of thing, extract that table, and then go and update all the necessary rows to the right things. It takes time... |
**Mat Ryer:** Yeah. I liked that you couldn't keep up because the machine was so fast. Is that why you now insist only on running on Raspberry Pi's? |
**Dee Kitchen:** Intel Max. Run on Intel Max. It's the solution for everything. \[laughter\] |
**Mat Ryer:** Okay, well that sound - we all heard that sound, didn't we? How would you describe that sound that we just heard? |
**Dee Kitchen:** Spooky... |
**Mat Ryer:** Natalie? Spooky, yes... Natalie, how would you describe that sound we've just heard? |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.