Wednesday, February 26, 2014

Episode 6: Michael Gough Part 2, video tutorials, and moving to Seattle, and a big thank you.

We had a great interview session with Michael Gough. That gentleman knows his way around malware, and I think his Sniper Forensic Toolkit would work great if you needed to secure several sensitive computer systems on the network. His Bsides Austin in March is shaping up to be really excellent. Red Team/Blue Team debate, speakers talking about safeguarding credit card info, and the Wednesday night talk on Windows logging is going to something special. Add to the price of attending the conference, you'd be crazy to not go. Plus, We've been asked to have a table at the conference! I would love to say we'll have swag, but all we'll have is Mr. Boettcher (hopefully!) will be doing drive by interviews. Please come on by, and he'll ask you probing questions, like favorite colors, favorite packet dumps, and Picard/Kirk preference. :)


During the post interview conversation, we talked about the Neiman Marcus alerts that were being generated, 60,000 alerts, and they still didn't see them going off. Here is the link to that article... Neiman Marcus

We would really like to do more interviews, but I worry about not showcasing our talents, so I will be working on some tutorial type videos. Nothing fancy, just testing the waters for more in-depth type applications. I wanted to start with an oldie, but a goodie... kismet. Show how to it up, configuring it to work with GPS, importing into Google Maps... incidentally, this will be a double feature with war driving. I'll get to work on my shaky cam skills too... but if I can get it to work, I'll be doing pretty well.


I'm sitting in my hotel room with my family, waiting to fly with my wife, daughter, and 3 furry children to Seattle, so my wife can work at a great job. I am able to work remotely, which is great, except the time zone is going to be a bit different for me. Plus, Mr. Boettcher and I will be 2 hours difference, which changes recording times for the podcast. We have the same issue on my other podcast (www.majortechnicality.com), since up until today, we were spread across 3 time zones. Things just got simpler, but we still have 3 hours between Dale, Jared, Farid, and myself. Change is good though. Makes for an interesting dynamic.


I just wanted to thank all of the people who have downloaded and/or listened to our podcast. Thanks to all of you, we've been accepted to iTunes, and we're getting to do what we love. Sharing info, talking about security, and having a good time. Plus, you probably get a few CPEs in the process.


Next week, we'll have part 1 of our interview with Kevin Johnson. A really great couple of interviews. Stay tuned!


Here is Part 2 of the Michael Gough Interview: Episode 6 Part 2

Thursday, February 20, 2014

Episode 6 Part 1: Michael Gough, Moon Pcap, Moving, and editorializing

Holy cow! We are in iTunes!!!

https://itunes.apple.com/us/podcast/brakeingdownsecurity-podcast/id799131292

We're in the big leagues now. I just noticed that this morning on our stats page from Libsyn... Apparently, people discovered us before I discovered myself. LOL


We had a great interview with Michael Gough (@hackerhurricane) from MI2Security about the malware that has been in the news recently. We talked a bit about how he would have done things differently if he was in the IT shop at Target.


One thing that we have to learn, as new podcasters in this industry, is to not editorialize. We cannot make statements of opinion as if they are a fact. We cannot say "Mr. Jones thinks X is fantastic", when he may not be all in on something.


It's a learning process, and thankfully, we learned it early, with someone who is cool and not pursuing legal action.


I (Bryan Brake) will be leaving the Austin area next week, and moving to the Pacific Northwest with my wife, who has taken a position with a small mom and pop software company up there. I'm going to be working remotely, which is always nice, but my job will be no less demanding of my time. I'll just have to adapt to 7am PST meetings. :) We'll still be having a podcast, next week is another interview with a person that Brian and I hold immense respect, both as a human being, and a security professional. You'll have to tune in to find out who. Use that spiffy new iTunes link. Now, we just have to figure out how to change the icon, and author, and everything...


Oh yea, was trolling Twitter the other day, and someone at @sans_isc posted a link to a pcap of the MOON self-replicating malware that is plaguing Linksys routers. I posted a link on the BDS homepage, so you can grab it. It goes to our Google Drive, so download and check it out, you packet weasels!!! MOON Pcap file


Without further ado, here's Episode 6, Part 1, with Michael Gough Link

Sunday, February 9, 2014

Episode 5: Interview with Frank Kim

Man, it was a great week. If you ever have the chance to go to a SANS Course, do it, and do it often. It may be expensive, but the networking opportunities are great, and the instructors are just good people.



During the "Capture the Flag", which I will not give out information about (so don't ask), I felt utterly useless. I had done all that I felt I could do, but it's amazing that you can take experiences from your own work and apply it to issues. Once we'd gotten in, I remembered something about a security issue at our office, and in doing so, I found a flag! I went from thinking I was a failure to being a hero of our team. What we didn't know was that another team had found all the flags, but because of a configuration issue on their browser, they missed a flag they'd discovered. If they'd not done that, they would have won.



But because of that mistake, our team capitalized on the the CTF, and won first place!



Mr. Boettcher and I had a blast over the week, networking with various people and instructors, meeting a tons of great people, hearing Robert 'RSnake' Hansen speaking at the SANS Summit, and just getting some really excellent training on tools like Burp, SamuraiWTF, Sqlmap, and others.



We also got several interviews in the can. Episode 5 is with Frank Kim, an Instructor with SANS, who was teaching the Secure Java coding class. We got him to sit down with us and discuss some of the issues dealing with the culture of secure coding

Have a listen: Frank Kim Interview

Sunday, February 2, 2014

Episode 4: Origin stories, and talking about mentoring and reconnaissance

Next week is going to be super hectic for your favorite co-hosts. Starting on Monday 3 February, we'll be taking SANS SEC542 in an effort to get our GIAC Web Pentest certs (GWAPT).


I haven't been this nervous since I went for my CISSP. Another company paid the skrill for that cert as well. Thankfully, I passed my CISSP on the first try. I was always excellent listening and retaining information in school, and I write a decent test.


But I know I'll prevail, because of excellent instructors like Kevin Johnson and Jason Lam. And I'll have my comrade in security Mr. Boettcher right alongside of me.


Anywho, enjoy the episode, we didn't have show notes, because of some logistical issues, our interview with Michael Gough had to get re-scheduled until after our class... but we are going to have that really soon, and it will be awesome.


Take care, we love the feedback, thanks to all those with positive feedback, and those with constructive feedback. We hear you, and are learning so we can do better.

Sunday, January 26, 2014

#15: Episode 3 of Brakeing Down Security: Alerts, Events, and a bit of incident response

As promised, I just uploaded Episode 3. We go into detail about alert levels, what types of events cause alerts, and why they should be investigated and mitigated. Take a listen, to it and all of the other podcasts we've done. I think you enjoy them.


If you are a security, compliance, or audit professional, and would like to come on our show, please hit me up on Twitter (@bryanbrake), or put a comment here on the blog. We'd love to have you on, and have a healthy debate.

Episode 3 on Libsyn

Here are the show notes:


Episode 3 show notes

Saturday, January 25, 2014

#14: The Prime Directive, malware, and having a ball

The Prime Directive in pentesting... "Don't do anything outside the scope document". It's like the Fight Club rule. You don't go outside the scope of the pentest. You don't go playing around in environments you shouldn't, even if it's there.


But what happens when the scope document was made by someone other than people with an intimate knowledge of the assets involved, and can be called ambiguous at best? Is this like Star Trek, where breaking the Prime Directive is bad, but you do your best to notify as best you can, and stop when or if someone raises a flag?


When your organization engages a company to do a pentest, defining what systems are being tested and locking your scope down is paramount to having a good operation. Even after the document is agreed upon, speaking with the pentester doing the operation can clear up any issues that can arise. If the pentester does happen to exceed scope, don't berate him unnecessarily. Thank him for notifying them of the findings, and then explain to them that they are outside of scope. If they continue to do so, you should report them. Often, they may have seen something so glaring that they are ethically bound to mention it. I know that if I was doing a pentest or evaluation and it was a bank or business I used, I would definitely find a way to let them know.


You want to get the most bang for your money, so you give the pentester a decent amount of time to test things. You may even want to run preliminary nmap scans, nikto scans (if web apps are involved), or vulnerability scanners. This is very important info for the beginning of a pentest, but often takes the longest to do by the pentester. This is menial stuff that is a waste of good pentesting time. Plus, a professional pentest shouldn't be adversarial in nature. Unless, of course, it's supposed to be... :)


I know in my last post, we were going to have an interview with Michael Gough (Twitter @hackerhurricane) from MI2 Security about Malware and APT attacks. In talking with him after our monthly ISSA meeting, we figured out that we could do a multi-part interview on Malware and APT. He also mentioned in our ISSA meeting that there had been 6 additional retailers that had been breached. We found out today (25 January) in a blog post from Brian Krebs, that Michaels' and it's subsidiary Aaron's Brothers were hit. That leaves 5 more retailers to through.


My guess is that WalMart is involved, and the only other one I'd imagine would be Kohl's... I don't know why, but those two are always on my mind when this story keeps coming up.


I never have had as much fun doing security as when I started this podcast, blog, and learning how to market ourselves. We are learning a lot about different subjects. It's also taken me out of my comfort zone quite a bit, because I'm not good at talking with people that I don't know, or soliciting input from strangers. I want to get my name, my brand out there, and my palms get sweaty just asking people if they'd like to come on our podcast. I'm sure that it will get easier. It's like learning to edit audio or video, you're gonna suck at it at first.


Episode 3 will be up late tomorrow night, just in time for your earballs to enjoy on your Monday morning commute. Hope you enjoy it. Our meeting with Michael Gough will take place Wednesday, and we'll be able to bring you that two or three parter in the weeks to come...

Sunday, January 19, 2014

#13: Vulnerability Scanners -- Episode 2

Episode 2 podcast

It's an odd thing editing audio. Some people make it look so easy. It helps having only two people on the podcast. This is not my first podcast to be on. My other podcast "Major Technicality", I am merely a contributor. And Jared, our producer, and co-host, spends several hours making everything sound just so.


Anyway, the audio will sound better on this one. Mic levels were dialed in, audio was normalized, and the crackling in the Intro is gone.


I really had a good time talking about vulnerability scanners. It's hard to believe that they've been around for over 20 years, and yet they haven't changed all that much. They still use concepts like banner grabbing, port scanning/knocking, and best guesses to scan a system for vulnerabilities. They should never be used as an end all be all, and truly on taken with a grain of salt.


Question all findings, trust nothing...


Next Friday, we'll be flush from our monthly ISSA meeting, which Michael Gough, from MI2 Security, will be discussing malware infection, and we are hoping to be able to get a few minutes with him. We'll have the interview spliced into the podcast, and we'll be able to continue our discussion about malware. Our first Interview! SQUEEEE!


I would have loved to speak about the other web application security scanners, but I really have only used Burp Suite. Brian and I will be attending SEC542 at the SANS convention 3-8 February in Austin, and we will definitely have one or more podcasts about web application pentesting and security assessment of websites.


Here are the show notes for this week:


Episode 2 show notes