Techno Security & Digital Forensics Conference East 2023
Tags: security, forensic, cybersecurity, owasp
Published: 2023-07-11 13:00:00

If you have ever heard of Wilmington, North Carolina, it might be because the [WW2 battleship North Carolina](https://battleshipnc.com/?ref=blog.gitguardian.com) is moored there, or that it is a historically significant [shipping town](https://www.starnewsonline.com/story/special/2021/02/27/wilmington-and-weldon-railroad-put-cape-fear-map-1800-s/4162030001/?ref=blog.gitguardian.com), or because of its [role in the US-British Revolutionary War.](https://allthingsliberty.com/2014/01/overlooked-wilmington/?ref=blog.gitguardian.com) But starting in 2023, it is also known as the east coast home for [Techno Security & Digital Forensics Conference](https://www.technosecurity.us/east?ref=blog.gitguardian.com), which was previously held in Myrtle Beach. 2023 also marked the 23rd year of the conference and community, this year bringing together just over 1000 total participants.

Many of the sessions were directed at law enforcement officers, leaning into the digital forensics side of the conference, and a lot of the attendees work with various government agencies. There were also plenty of sessions for the general security community as well. Here are just a few of the highlights from this enlightening cybersecurity event.

![](https://blog.gitguardian.com/content/images/2023/06/Fx4mUeSWIAEB0eg.jpeg)

## Improving our security posture

### Security special forces

In the keynote "Cyber Defense is the New Offense," [Joseph "Rich" Baich, CISO at the CIA](https://www.linkedin.com/in/richbaich/?ref=blog.gitguardian.com), shared how the cyber threat landscape continues to evolve. He began his talk by reminding us of the uphill challenge we all face: adversaries only need to be right once, while we must be ever vigilant and continually improve.

In our jobs to take the battle to the attacker, Rich referenced the martial art of Judo. in Judo, you are trained to lead your opponent to do something else than they initially set out to do, specifically something you can counter. In cybersecurity, this is exactly what we need to do through cyber deception, driving them to another part of the network where we can attack them.

We should take action to drive the cost up for adversaries to succeed. We know how they behave, and their operating procedures are pretty standard: They establish a beachhead, lateral expansion, and privilege escalation.

Embracing Zero Trust is another essential step in protecting our organizations. This means starting from a position of disallowing everything. We then need only to allow essential access, be that to a person or a service. Similarly, if we always start from a position requiring Multi-Factor Authentication, MFA, then it will be much easier to keep access locked down.

Rich suggested partnering with government agencies or at least being ready to when needed. In the US, for example, [CISA](https://www.cisa.gov/?ref=blog.gitguardian.com) and [DHS](https://www.dhs.gov/?ref=blog.gitguardian.com) have a lot of taxpayer-funded resources simply awaiting your requests. They can also be there when cybercriminals are actively attacking you, which you should prepare by pre-drafting lawyer-approved letters that allow you to share data and techniques with the government. He said this would save a lot of time and money in the long run; no one wants to call their lawyer in the middle of an incident to draft this after the fact.

Rich ended his session by encouraging us all to adopt a 'special forces' mentality, summed up in five truths:  
1\. Humans are more important than hardware.  
2\. Quality is better than quantity.  
3\. Competent special forces can not be created after an emergency occurs.  
4\. Special forces can not be mass-produced; they take individual time and attention.  
5\. Remember that special operations require non-special operation support. We can't do this alone.  

[![](https://blog.gitguardian.com/content/images/2023/06/Fx8EG9FWYAQACpb.jpeg)](https://twitter.com/McDwayne/status/1666054909718872065?ref=blog.gitguardian.com)

### Enabling better security culture

In his session "True Cyber Emergency Stories and Leadership Action Plans," [Dan Lohrmann, Field CISO of Presidio](https://www.linkedin.com/in/danlohrmann/?ref=blog.gitguardian.com), reminded us that ransomware is a very real and ongoing threat. At the time of this writing, the [City of Dallas](https://www.scmagazine.com/brief/ransomware/dallas-ransomware-recovery-nearly-completed?ref=blog.gitguardian.com) has been fighting an ongoing attack for months. Cybersecurity is a business risk issue, not just an IT issue. Supply chain attacks are opening eyes that it is not 'if,' but "when" an incident will occur.

He stressed we must practice like we want to perform. We must start to think in terms of real-world situations and not ideal circumstances. For example, in tabletop exercises, he gives a randomly chosen 1/3 of the room the 'day off,' not letting them participate. In day-to-day life, the reality if some essential team members will be sick, on vacation, or just unavailable in general

We need to think about ransomware as we do hurricanes, floods, and natural disasters. Do you have our plans backed up offline or at least off the network? Do you have a backup power supply?

While we live in a scary world, we can allow fear, uncertainty, and doubt (FUD) to dominate our cybersecurity programs. We must learn to enable, not disable, our teams and orgs. We all need to strive to be seen as enablers and trusted advisors. If you are seen as continually saying, "No, we can't do that," then you will not be trusted to empower the organization when there is an emergency.  

[![](https://blog.gitguardian.com/content/images/2023/06/FyBTvLeX0AA27kr.jpeg)](https://twitter.com/McDwayne/status/1666423939164250114?ref=blog.gitguardian.com)

[#TechnoSecurity](https://twitter.com/hashtag/TechnoSecurity?src=hashtag_click&ref=blog.gitguardian.com) day 3 kicks off with "True Cyber Emergency Stories and Leadership Action Plans" Dan Lohrmann, Field CISO at [@Presidio](https://twitter.com/Presidio?ref=blog.gitguardian.com)

### Security for any size budget

We heard a lot of straightforward security best practices from [Robert Wagner](https://www.linkedin.com/in/robertwagner2/?ref=blog.gitguardian.com) in his talk "Blue Team on a Budget." His main takeaway is that no matter how large or small your organization's security budget is, there is no reason security shouldn't be implemented.

Organizations tend to focus too much on technical solutions, forgetting that processes and people are just as crucial in our security equations overall. One way to get people more actively involved in security is by making it fun through contests and competitions to report the most phishing attempts or malicious sms messages, for example. For the price of a few Amazon or Starbucks gift cards, any org can turn entire non-technical departments into 'carbon-based threat detectors.' Training them to use password managers and to stop storing passwords under keyboards can go very far in keeping them safe.

Another very cost-effective measure is patching out-of-date software. An additional easy win could be blocking outgoing server access to everywhere it is not explicitly allowed. Blocking all executables from running that are not on an explicitly allowed list can also shut down many attacks.

Robert also suggested laying down some landmines in the form of canaries or honeytokens within your perimeter as well. No attacker in the world is going to pass up a file called "PasswordList," which you could stuff with decoy credentials. We 100% agree [honeytokens are a great too](https://www.gitguardian.com/honeytoken?ref=blog.gitguardian.com)[l](https://www.gitguardian.com/honeytokenhttps://www.gitguardian.com/honeytoke?ref=blog.gitguardian.com).

[![](https://blog.gitguardian.com/content/images/2023/06/Fx4M-7TWAAYrORm.jpeg)](https://twitter.com/McDwayne/status/1665783193373495296?ref=blog.gitguardian.com)

[#TechnoSecurity](https://twitter.com/hashtag/TechnoSecurity?src=hashtag_click&ref=blog.gitguardian.com) keeps rolling with great content from legendary presenter [@Mr\_Minion](https://twitter.com/Mr_Minion?ref=blog.gitguardian.com) presenting "Blue Team on a Budget" When we focus too much on the tech side for security, we end up with orgs that look like this...

## AI and the future of security

ChatGPT and AI are hot topics in most current cybersecurity conversations, and that is exactly what [Ian O’Briant from CheckPoint](https://www.linkedin.com/in/ian-o-briant-46412785/?ref=blog.gitguardian.com) explored in his session "Artificial Intelligence: Friend or Foe in the Context of Ransomware." Unfortunately, ransomware continues to be a growing threat, with the number of attacks increasing by 93% since the start of the year. Over the last couple of years, we have even seen the rise of "[ransomware-as-a-service](https://www.crowdstrike.com/cybersecurity-101/ransomware/ransomware-as-a-service-raas/?ref=blog.gitguardian.com)."

Ian explained we are in the middle of the AI revolution. In the last major shift, the industrial revolution, we had a transformation of muscle power being replaced by machine power. In this AI age, we are replacing brain power with machine power, or now, AI power. This is all driven by ever cheaper memory and ever cheaper hardware that you can now simply rent.

While we often hear about the ways criminals use AI tools like ChatGPT to write malware, the good guys are also making strides forward too. Ian walked us through how his team uses AI for Predictive Threat intelligence, exposing [C&C](https://www.trendmicro.com/vinfo/us/security/definition/command-and-control-server?ref=blog.gitguardian.com) servers and malicious domains faster than humans alone have ever been able to.

For examples of this, he brought up tools like Checkpoint's [Huntress and CADET](https://blog.checkpoint.com/security/ai-and-cybersecurity-combining-data-with-human-expertise/?ref=blog.gitguardian.com). Teams are able to leverage these tools to stop malware more effectively at the edge before those phishing emails ever enter email servers or hackers can gain a foothold. Combining predictive intelligence with best practices like MFA, keeping patches up to date, and strong content disarm & reconstruction, CDR, processes, we can stop the most common attacks and keep our orgs safe, even as threats evolve.

[![](https://blog.gitguardian.com/content/images/2023/06/Fx3vlW-XwAACOm8.jpeg)](https://twitter.com/McDwayne/status/1665750867713175553?ref=blog.gitguardian.com)

[#TechnoSecurity](https://twitter.com/hashtag/TechnoSecurity?src=hashtag_click&ref=blog.gitguardian.com) keeps on rolling with [#cybersecurity](https://twitter.com/hashtag/cybersecurity?src=hashtag_click&ref=blog.gitguardian.com) content with "Artificial Intelligence: Friend or Foe in the Context of Ransomware" by Ian O’Briant from [@CheckPointSW](https://twitter.com/CheckPointSW?ref=blog.gitguardian.com)

## ZAP

One of the best parts of open source tools is that they easily fit into any sized budget and still deliver amazing results and value. This was one of the many takeaways from the session "Open Web Application Security Project (OWASP) Zed Application Proxy (ZAP): Is My Web App Secure or Vulnerable?" by [James Dodmead from Cyber Defense Solutions](https://www.linkedin.com/in/jim-dodmead-699b706/?ref=blog.gitguardian.com).

While there is no silver bullet in security, testing can prevent a lot of issues and save a lot of headaches. While static scanning tools, [such as secrets scanning](https://www.gitguardian.com/monitor-internal-repositories-for-secrets?ref=blog.gitguardian.com), are fantastic, dynamic scanning of a live application can uncover different types of problems. Fortunately, one of the best dynamic application scanners in the world is free and open source: [OWASP ZAP](https://www.zaproxy.org/?ref=blog.gitguardian.com).

ZAP, short for Zed Attack Proxy, is a tool that sits between your browser and an application. It features a lot of capabilities, including:  
\- A spider - to crawl web apps to find all paths,  
\- Passive scan - injects nothing into the application and just reports on what is returned from requests,  
\- Active scan - an attack mode to be used only on applications that you have explicit permissions to attack.  
\- Fuzzing - submitting lots of invalid or unexpected data to a target.

It comes with a choice of UI options, with a classic app frontend that displays lists and a folder view of issues when you first start the application. There is also a [Heads up Display, HUD](https://www.zaproxy.org/docs/desktop/addons/hud/?ref=blog.gitguardian.com), that shows up as an overlay on top of the application in your browser.

James repeatedly reminded us that using ZAP in active scanning mode means you are actively attacking a web app. This is illegal unless you either own the app outright or have express written permission from the owners. Fortunately, for testing purposes, OWASP has another project you can freely download and use, [Juice Shop](https://owasp.org/www-project-juice-shop/?ref=blog.gitguardian.com). When run locally in a Docker container, you can test and experiment as much as you like, for free and completely legally.

James also left us with parting suggestions for free online security training. He suggested leveraging the free training course on [Web Security Academy offered by Portswigger](https://portswigger.net/web-security?ref=blog.gitguardian.com). He also pointed us to the [National Vulnerability Database feeds](https://nvd.nist.gov/vuln/data-feeds?ref=blog.gitguardian.com) and urged us all to stay up to date on the ever-evolving threat landscape.

[![](https://blog.gitguardian.com/content/images/2023/06/Fx4YnT-XsAAJ7Kq.jpeg)](https://twitter.com/McDwayne/status/1665795982250917893?ref=blog.gitguardian.com)

[#TechnoSecurity](https://twitter.com/hashtag/TechnoSecurity?src=hashtag_click&ref=blog.gitguardian.com) continues in the afternoon with James Dodmead presenting abotu one of my favorite [#OWASP](https://twitter.com/hashtag/OWASP?src=hashtag_click&ref=blog.gitguardian.com) tools: Open Web Application Security Project (OWASP) Zed Application Proxy (ZAP): Is My Web App Secure or Vulnerable?

## Data-driven decisions making

Closing out the whole event was one of the most charismatic speakers I have ever had the opportunity to see. Dr. Joe Perez presented "Driving Decisions with Data: Delight or Disaster?" Rather than try and summarize his fantastic talk, I am going to simply encourage everyone to [watch a recording of this same talk](https://www.youtube.com/watch?v=2AIYHYGIf9I&ref=blog.gitguardian.com) from a previous event he keynoted.  

[![](https://blog.gitguardian.com/content/images/2023/06/FyHCTbFXoAEC_hI.jpeg)](https://twitter.com/McDwayne/status/1666826979444768768?ref=blog.gitguardian.com)

The final session of [#TechnoSecurity](https://twitter.com/hashtag/TechnoSecurity?src=hashtag_click&ref=blog.gitguardian.com) is "Driving Decisions with Data: Delight or Disaster?" by the one and only Dr. Joe Perez, Senior Systems Analyst / Chief Technology Officer - NC Dept of Health & Human Services / SolonTek Corporation

## Keeping us safe is everyone's responsibility

The Techno Security & Digital Forensics Conference is a wonderful community, bringing together the folks on the front lines of cyber warfare, academics researching emerging and evolving threats, and industry professionals like myself focused on providing technical solutions to help us improve our security posture. It is through events like this that cybersecurity professionals can really grow and learn. I am very grateful to have had the chance to be part of it, sharing my knowledge about [what to do when a secret leaks](https://www.technosecurity.us/east/2023-conference-program/credentials-leakednow-?ref=blog.gitguardian.com).

Whether you are building tools to catch malicious actors or just trying to make your internal org safer, GitGuardian can help you do it with more confidence around secrets management. Detecting leaked secrets quickly and accurately is just as important as storing and managing those credentials safely. Using [GitGuardian Secret Detection](https://www.gitguardian.com/monitor-internal-repositories-for-secrets?ref=blog.gitguardian.com) can keep you on top of your secrets management game no matter how large your development team gets or how many repos you have. Combined with [GitGuardian Honeytoken](https://www.gitguardian.com/honeytoken?ref=blog.gitguardian.com) for immediate intrusion and leak detection, you can feel confident your secrets will really stay secret.

[![](https://blog.gitguardian.com/content/images/2023/06/FySdWbjWwAIdW7L.jpeg)](https://twitter.com/craighewett/status/1667630776848982017?ref=blog.gitguardian.com)

[**𝐂𝐫𝐚𝐢𝐠 𝐇𝐞𝐰𝐞𝐭𝐭**](https://twitter.com/craighewett?ref=blog.gitguardian.com)[@craighewett](https://twitter.com/craighewett?ref=blog.gitguardian.com)The tall ship [@lanaosantamaria](https://twitter.com/lanaosantamaria?ref=blog.gitguardian.com), a replica of the Nao Trinidad, currently docked in [#WilmingtonNC](https://twitter.com/hashtag/WilmingtonNC?src=hashtag_click&ref=blog.gitguardian.com).