The Most/Recent Articles

Showing posts with label nccdc. Show all posts
Showing posts with label nccdc. Show all posts

Daily Blog #748: National CCDC 2025

 


 

Hello Reader,

For over 15 years, I’ve had the honor of serving as the red team captain for the National Collegiate Cyber Defense Competition (NCCDC). Since its inception in the early 2000s, NCCDC has evolved from a  a handful of schools into a premier, nationwide event that now attracts teams from over 180 institutions across the country. This competition is more than just a contest—it’s a rigorous, real-world simulation where our nation’s next generation of cyber defenders learn to tackle emerging threats head-on (us).

At NCCDC, we simulate live attack scenarios, leveraging the very tools and techniques that threat actors use in the field. Every year, I bring together the most effective strategies and custom tooling I've encountered in my real worfk, challenging collegiate teams to defend against sophisticated, dynamic cyber engagements. The environment is intense, and every engagement is a testament to the creativity and resilience of our future security professionals. Don't feel bad for these college students they train all year long to have a chance of locking us out.

What truly sets NCCDC apart is its lasting impact on participants. Many past competitors have gone on to become leaders in the cybersecurity world—working with top-tier companies, federal agencies, and innovative startups. Our alumni network is a vibrant community of experts who continue to shape our nation’s cybersecurity landscape, using the skills honed in these competitions to safeguard our digital future. 

Now, as we gear up for another exhilarating season, I’m reaching out to all skilled individuals ready to step into one of the best cyber simulations on the planet. Ever year I put out a call for the limited number of volunteer spots for our red team—those with a knack for thinking like an adversary. If you have a proven track record demonstrated by a robust GitHub portfolio, innovative custom tooling, and a passion for making our digital world more secure, we want to hear from you.

This is your chance to:

  • Challenge Yourself: Engage in realistic simulations that push your skills to the limit.
  • Inspire Future Defenders: Share your expertise with tomorrow’s cybersecurity leaders.
  • Be Part of a Legacy: Join a community whose alumni have gone on to make significant impacts in cybersecurity nationwide.
  • Be Destructive: We are one of the few competition that allows the red team to take down blue team infrastructue and forces them to rebuild and defend.

If you believe you have what it takes to survive in one the best cyber simulation engagements, please email your resume and GitHub portfolio to dlcowen@gmail.com.

Also Read: What I look for when reviewing external ips


Daily Blog #662: Forensic Lunch 4/3/20 - Discussion on WinSCP, Linux Forensics Course, SANS DFIR, and More

Discussion on WinSCP, Linux Forensics Course, SANS DFIR, and More


Hello Reader,
   Today we had another episode of the Forensic Lunch!

On this episode:

You can watch the show below:

Also Read: Daily Blog #661

Daily Blog #556: NCCDC Red Team Call for Volunteers

NCCDC Red Team Call for Volunteers - David Cowen - Hacking Exposed Computer Forensics Blog



Hello Reader,
         It's coming around to CCDC competition time for much the of the United States, some schools are already in invitationals. This is the yearly call for volunteers for the NCCDC red team. If you have the following to bring to the table:


  • Custom malware
  • Custom command and control 
  • An active Github repository 
  • The ability to lay low and persist with an active defender
If so, email your cv to volunteer@nccdc.org Spots are limited each year for volunteers and we hope to hear from you. 

Also Read: Daily Blog #555

National CCDC 2018 Redteam Debrief

National CCDC 2018 Redteam Debrief by David Cowen - Hacking Exposed Computer Forensics Blog



Hello Reader,
       Another year of CCDC is over and another winner has been crowned.

For those of you just here for the presentation, here are this years debrief slides:

https://www.dropbox.com/s/o2fkwbjsefq1ixk/NCCDC2018.pptx?dl=0

For those of you looking for more:

This year at Nationals we had a lot of success as a red team From 0 knowledge (Except ips in scope) to plain text credentials in 3 minutes ensured that our initial load of persistence was successful. However like in all great pursuits it was not perfect. This year we attempted different delivery and propagation techniques that need to validate our malware was successfully implanted to make sure all systems are talking to us.

Speaking of talking to us this year teams got better at their egress filtering and locking down incoming services. This means we have to get better at backdooring existing services and work on techniques that don't require call backs that egress filtering will stop.

Lots to plan, lots to do for next year. 


National Collegiate Cyber Defense Competition Red Team Debrief 2017

National Collegiate Cyber Defense Competition Red Team Debrief 2017



Hello Reader,
        I've been busy lately, so busy I didn't get around to posting this years red team debrief from the National CCDC. After just leaving Blackhat/ Bsides LV/ Defcon and running our first Defcon DFIR CTF I thought it was important to get these up and talk about the lessons learned.

The Debrief

First of all for those of you coming just to get the presentation its below:
here: https://www.dropbox.com/s/fy23c7wi35qe81b/NCCDCRedTeamDebrief2017.pptx?dl=0

For those of you who have no idea what any of these means, let me take a step back.

What is CCDC?


The National Collegiate Cyber Defense Competition ( CCDC ) is a now 12 year old competition where colleges around the United States form student teams to defend networks. CCDC is different from other competition involving network security as it focuses strictly on defense. Students who play are put in charge of a working network that they must defend, the only offensive activity in the competition comes from a centralized red team.

The kind of enterprise network students take charge of changes each year. Past years business scenarios have included:

  • Private Prison Operator
  • Electric Utility
  • Web hosting
  • Game Developer
  • Pharma
  • Defense Contractor
  • and more!
The idea is that the last IT team has been fired and the student team is coming in to keep it running and defend it. While the students are working on making sure their systems are functioning they also have to watch for, respond to and defend against the competition red team. 

Scoring happens a couple ways. 

Students get points for:
  • Keeping scored services running (websites, ecommerce sites, ssh access, email, etc..)
  • Completing business requests such as policy creation, password audits and disaster recovery plans
  • Presenting their work to the CEO of the fake company
  • Responding to customers 


Students lose points for:

  • Red team access to user or administrative credentials
  • Red team access to PII data
  • Services not responding to scoring checks aka services being down
  • SLA violations kick in if the service stays down for a period of time
There are now 160 universities competing in 10 regions across the united states. If a student team wins their region they make it to nationals where the top 10 teams in the country compete for some pretty amazing prizes, including on the spot job offers from raytheon. 


If you are a student or a professor who would like to know more about competing you can go here: http://nccdc.org/index.php/competition/competitors/rules

What is the National CCDC Red Team?

The National CCDC Red Team is a group of volunteers who works to build custom malware, c2 and exfiltration and persistence strategies to bear each year to give the students the best real world threat experience. I'm the captain of the red team and have been for the last 10 years.



How do I get on it? 

When the call for volunteers goes out send a resume to volunteer@nccdc.org.

Be advised our threshold for acceptance is very high and we look for the following:
- Active projects on github or otherwise to show your experience
- Real experience in developing, maintaining and layering persistence
- Custom malware kits that are unpublished to bring to bear

We don't care about certs, years of experience or who you work for. We need people who can not only get in (the easy part) but to stay in over a two day period of competition while an aggressive group of defenders seeks to keep you out. 


Daily Blog #381 National CCDC Redteam Debrief

National CCDC Redteam Debrief by David Cowen - Hacking Exposed Computer Forensics Blog



Hello Reader,
     The 11th year of the National Collegiate Cyber Defense Competition has ended, congratulations to the University of Central Florida for a their third consecutive win. I hope you make it back next year for another test of your schools program and ability to transfer knowledge to new generations of blue teams.

If you want to show your support for my efforts, there is an easy way to do that. 

Vote for me for Digital Forensic Investigator of the Year here: 



However the team that won over the Redteam was the University of Tulsa who came with a sense of humor. Behold their Hat and Badges:
National CCDC Redteam Debrief by David Cowen - Hacking Exposed Computer Forensics Blog


Also you have to check out the player cards they made here:
https://engineering.utulsa.edu/news/tu-cyber-security-expert-creates-trading-cards-collegiate-cyber-defense-competition/

Here is an my favorite:
National CCDC Redteam Debrief by David Cowen - Hacking Exposed Computer Forensics Blog


You can download my Redteam debrief here:
https://drive.google.com/file/d/0B_mjsPB8uKOAcUQtOThUNUpTZ0k/view?usp=sharing



National CCDC 2015 Red Team Debrief

National CCDC 2015 Red Team Debrief
Hello Reader,
              Here is this years Red Team debrief. If you have questions please leave them below.

https://drive.google.com/file/d/0B_mjsPB8uKOAWnY5ZERHX0RUWEU/view?usp=sharing


Daily Blog #310: NCCDC RedTeam Debrief Slides

NCCDC RedTeam Debrief Slides by David Cowen - Hacking Exposed Computer Forensics Blog

Hello Reader,
                 Well the Raytheon National Collegiate Cyber Defense Competition has ended for 2014 with the University of Central Florida taking the Alamo cup home with them. For those not familiar CCDC is a network defense competition that colleges around the united states compete in. For the nationals the top 10 teams in the nation who have one their regional qualifier come to face my red team while trying to normally operate their businesses. At the end of the event I present a debrief of what the red team did and what they should have learned from it to be better at defending and responding in the competition and real life.

Here are my slides:
https://drive.google.com/file/d/0B_mjsPB8uKOALXNpRE9FeUk2NGc/edit?usp=sharing

If you are a current or former competitor, or just interested in the event, and have questions about what we did this year I will be doing a Reddit AMA on 2pm CST.  You can participate here:
http://www.reddit.com/r/IAmA/comments/24a0dg/iama_red_team_captain_for_the_national_collegiate/

Hopefully I can keep the AMA going for a couple hours while I finish work for the day, but I'll likely check back for unanswered questions later in the evening as well.

Also Read: Daily Blog #309

Daily Blog #290: National CCDC is coming

National CCDC is coming by David Cowen - Hacking Exposed Computer Forensics Blog

Hello Reader,
        It's almost that time of year again, National Collegiate Cyber Defense Competition time! Every year for the past 7 years I've been leading the national red team in what I can only call a weekend of fun and stress relief. This year 130 US colleges put together teams of undergraduate and graduate students to learn real world defense skills under the pressures of normal business needs. This year the event has grown again with Raytheon as a named sponsor who have brought a lot of their own resources to bear to the event, including the following very cool infographic.

National CCDC is coming by David Cowen - Hacking Exposed Computer Forensics Blog

So 10 college teams representing the best cyber defense talent in the nation are coming to San Antonio this month to see who can hold their network together against my teams attacks while also keeping the lights on for the business they are trying to protect. At the conclusion of the event I usually give two talks to the students. One in a conference type setting where I try to explain better IR skills and new response techniques and the other a red team debriefing. As in past years I'll post those slides here when I do.

Wish the 10 teams luck, they'll need it!

Also Read: Daily Blog #289

NCCDC 2013 Lessons Learned

NCCDC 2013 Lessons - David Cowen

Hello readers,

For those who are not familiar, the National Collegiate Cyber Defense Competition (NCCDC) is held once a year in San Antonio, Texas. The 10 winning teams from regionals held across the united states come to San Antonio to prove their abilities against an active and aggressive attacker  while at the same time completing business objectives and dealing with simulated customers/users. It's only open to teams of college students and they train through the year and begin the qualification process in late winter.

 I am the captain of the NCCDC red team and have been for 7 years now and in those 7 years we've expanded and grown as a red team to deliver what I would like to think is a unique and compelling experience to the student teams.

On of my redteamers, Alex Levinson, posted a blog with his takeaways from being a CCDC bad guy. You can read it here: https://alexlevinson.wordpress.com/2013/04/24/ccdc-2013-red-team-feedback/

Raphael Mudge gives a more thorough accounting of this years tricks in his write up: http://blog.strategiccyber.com/2013/04/24/national-ccdc-red-team-fair-and-balanced/

I thought I would follow up as promised and give a break down that goes beyond the slide show I posted in the previous post. When I give my redteam debrief I try to collect the screenshots from around the redteam that best illustrate the mistakes that we see made during the competition. As I write this post I've realized its important that I detail more about what we do at national ccdc as a red team for those of you that have never  experienced our welcoming redteam hospitality. As the red team captain I have several duties:

1. Set the strategy for this years attacks.

2. Make sure the best possible volunteers are located and brought in to bring the best possible redteam to bear against teams shown to be capable enough to survive the other redteams on their journey.

3. Restrict access to the redteam room to prevent distractions.

4. The assignment of redteam members to teams.

5. Make a room full of usually solo penetration testers work together and follow my plan.

6. Talk to tour groups as they are escorted into the redteam room to explain how we operate, our plan and to prevent them from distracting the redteam.

7. To force communication and cooperation across the different redteam members so all student teams receive the same love.

8. To assist in cultivating custom toolkits, backdoors and tools and get communication started before the event so that everyone knows what is possible.

9. To enforce the rules of the competition to make sure no redteam member voids the provisions put in place to insure a fair contest.

10. To make sure the students meet their redteam members and that they hopefully learn something from the experience.

11. Facilitate requests between the redteam and the gold team.

12. Take care of my own assigned student team in making sure I leave behind my own presents.

13. Make sure all the red team members fill out their incident submissions.

In short, I have lots to do over the weekend and over the years I've learned alot from the process. I even did a talk at derbycon lat year about what I've learned: http://www.irongeek.com/i.php?page=videos/derbycon2/david-cowen-running-a-successful-red-team If you are running a red team I recommend you watch it.

So after explaining all of that, here is what I think student teams and the industry in general needs to consider when defending.

1. Reinstall is not the solution for remediation

This idea that reinstalling is the best way to recover from an intrusion is something that is not isolated to CCDC students, its a common trend in the industry. However as a CCDC competitor you are under a microscope with an attacker who knows you have to put that system back up as soon as possible to stop the bleeding.

This in the short term is true, however in the long term (as in the rest of the competition) its a faulty perception. The SLA violation you take for having your services down is the largest continual point disruption we can generate as a redteam, all other actions we take against you are one time/one point deduction activities. We bring a bag of tricks to NCCDC but we don't have the time a real world attacker does to continually generate new tools/new techniques in the span of two days. Once you detect and block our years sneaky du jour you will have effectively blocked us for the rest of the competition in a form that will scale to the rest of your systems. This means that in the long term you can keep us out, keep your systems up and your SLA violations to a minimum.

Failing to do this an reacting to the short term access will just cause the same pain to reoccur. This creates a race between you and the redteam to see who can get back into your system faster once you've restored and then take the system down again .. hopefully before the scoring engine checks for an update and you are just continually seen as being down. The SLA violation grows for each period your down, keeping you down  is a tactic not just a funny thing to do.

2. Logfiles are important and part of a bigger picture of data

Past teams were quite observant of the logs to their external services, current teams have seem to lost the art. Watching logs for the services you are providing externally and for errors and login events will help you go a long way in proactively detecting our accesses, probes and intrusions. Beyond the default logs being created for you, learn how to configure them to add additional information to capture more of what we are doing.

3. You have to understand normal to identify abnormal

This may be the most important bit of advice, and the hardest to understand. You need to have worked with an operating system long enough to know what processes, behaviors, files, activity is part of the actual operating system. The only way to do this is with practice, installing and working with different parts of the operating system and seeing what changes, gets added, gets deleted, gets executed.

Once you've learned what is normal, what accounts should own processes, what ports should be open, what ips defined services should be communicating with, etc... Our activities and especially our persistence will stand out much more. Watching a team launch TCP View while you watch them and they don't notice your connection means they are hoping for some giant flag saying 'HACKER FOUND' rather than understanding what traffic is abnormal/bad.

4. Knowing your operating system outside of a google search is important

I understand we all use google, I use google and other search engines every day. However, if to quickly manage and configure your operating system and its services you have to turn to google then you've created a problem. You should know the system and the commands well enough before competition to be able to secure your system as quickly as possible and bring up new services without us watching you google instructions for the next hour as you stumble.

5. Knowing your applications/services capabilities is the only way to secure them

If you encounter a new application either that you have to install or that you find already running the first things you need to understand are:

1. How to administer it locally
2. Does it have default credentials
3. Does it have remote administration capability
4. Search the documentation for security configuration
5. Find out where the application creates logs and error logs
6. Does it connect to another service/database

Then go back through 1-6 and lock it down. We are doing the same thing on the red team side, after all these things fail to get us in will we then start a code review/known exploit search .

6. Learn some basic Incident Response tools and techniques

Alex Levinson said something particularly insightful one evening over margaritas, "When I was a student I saw CCDC as a system administration contest, but really its an Incident Response contest". I think there is alot of truth to this, most students focus on how to install, configure and setup the operating system. Some students get interested in the red teaming aspect of it, but very few get interested into the forensics and incident response aspect of CCDC.

Forensics is what I do for a living so maybe I'm a bit bias, but the amount of grief you could save your team and the number of points you could recoup from our attacks is enough to make at least one person of your team the incident responder. They should focus on the following:

1. Learn how to capture live memory

2. Learn how to use volatility to find possible malware

3. Learn how to scan for alternate data streams.

4. Learn how to work with forensic artifacts such as prefetch and the application compatibility cache.

5. Learn how to make and scan timelines for malicious activities.

6. Capture network traffic and look for us.

Doing this does not take as long as you think once you get good at it and in doing so you will be able to identify, detect, respond and eliminate us and our persistence.

Next year will be harder, I warn you now. I have plans blue teams and you are are the center of them. Take this blog post as a warning and be ready.


I'll be doing an AMA on reddit Monday April 29th 2013 at 1:30pm if you want ask questions or you can leave comments below.

Also Read: NCCDC 2013 Wrap up

NCCDC 2013 Wrap up

NCCDC 2013 Wrap up


Greetings Reader,
                     Another year and another NCCDC is done. While the red team always wins we are happy to share our victory with this years winner RIT. Every year I present a debrief to the teams that make it to nationals to highlight the common mistakes they make and how they can improve. This years theme was 'Intervention' as we felt the teams overall didn't seem to be improving as we keep escalating our tactics. Here is this years debrief:

http://sdrv.ms/13JOgGg

There was video taken this year and a documentary crew from UTSA. I'll post the video and a more detailed breakdown of our activities this year tomorrow.


NCCDC 2012 Wrap up post

NCCDC 2012 Wrap up post


Hello Friends,
                        This post is here to give links to the two presentations I gave at NCCDC for those interested and contacts to red team members for those interested in knowing more about what happened to them.

Red Team Debrief PPT: https://skydrive.live.com/redir.aspx?cid=c252230f74663370&resid=C252230F74663370!848&parid=C252230F74663370!126&authkey=!AEdgB9WG-fF3pd0

Responding to the incident: https://skydrive.live.com/redir.aspx?cid=c252230f74663370&resid=C252230F74663370!849&parid=C252230F74663370!126&authkey=!ADnYRFJV9VCMK08

Red Teamers:
Mubix @mubix on twitter
Chris Nickers: @indi303 on twitter
Ryan Jones: @lizborden on twitter

i'll get more email addresses and twitter names and update this post as I hear back from them.

If you would like to watch the red team debrief, albeit with some bad audio, you can watch it here:
http://t.co/4umtDJnB

Also Read: See you at CEIC

NCCDC is coming - My favorite time of year

NCCDC is coming - My favorite time of year


Once a year the fine folks at the National Collegiate Cyber Defense Competition invite a team of people to participate in their event as red or white team members. I'm happy to announce that I've been asked to return as captain of the red team this year again on April 8-10 in San Antonio, Texas. I got my start as a professional in network security and though I speak about computer forensics publicly we at G-C still do network security for select clients.

For those not familiar with CCDC it is a national competition that pits teams of college contestants who have to defend their network while continuing to deploy new business services against a team of people who are looking to ruin their day.While there is always a team who wins the national title I've always felt that it's the red team who always wins since we have the most fun.

Getting involved with CCDC is something I've always enjoyed doing and would recommend others do as well, if you are looking to volunteer as either a good guy or a bad guy you should go here http://www.nationalccdc.org/index.php?option=com_content&view=article&id=58&Itemid=70 to get involved at either the national or local levels.


If you are company looking to recruit the best talent emerging out of today's universities you could also benefit by sponsoring, as we have, the event and get access to these students before they can write their own ticket. To sponsor go here:  http://www.nationalccdc.org/index.php?option=com_content&view=article&id=59&Itemid=37

Also Read: Oh no, it's GroupWise!