Gray Hat Hacking The Ethical Hackers Handbook, 3rd Edition - podcast episode cover

Gray Hat Hacking The Ethical Hackers Handbook, 3rd Edition

Apr 05, 202625 min
--:--
--:--
Download Metacast podcast app
Listen to this episode in Metacast mobile app
Don't just listen to podcasts. Learn from them with transcripts, summaries, and chapters for every episode. Skim, search, and bookmark insights. Learn more

Episode description

Gray Hat Hacking: The Ethical Hacker’s Handbook, Third Edition serves as a comprehensive technical guide for security professionals and researchers. The text outlines various cybersecurity disciplines, ranging from the legal and ethical frameworks of disclosure to advanced exploitation techniques involving Linux and Windows systems. It provides detailed instruction on penetration testing methodologies, including social engineering, physical security breaches, and the use of professional tools like Metasploit and BackTrack. Additionally, the content covers specialized topics such as malware analysis, reverse engineering, and securing SCADA or VoIP systems. Beyond the core handbook, the sources highlight expert-led certification training for the CISSP exam and a broader series of "Hacking Exposed" literature. The collective material aims to equip "gray hat" practitioners with the offensive knowledge necessary to build more robust defensive infrastructures.

You can listen and download our episodes for free on more than 10 different platforms:
https://linktr.ee/cyber_security_summary

Get the Book now from Amazon:
https://www.amazon.com/Gray-Hacking-Ethical-Hackers-Handbook/dp/0071742557?&linkCode=ll2&tag=cvthunderx-20&linkId=c0f44a9aceaee1201dba28d14b5053e2&language=en_US&ref_=as_li_ss_tl

Discover our free courses in tech and cybersecurity, Start learning today:
https://linktr.ee/cybercode_academy

Transcript

Speaker 1

You know, when military fighter pilots are prepping for combat, they don't just sit around in a classroom staring at the technical specs of their own jets.

Speaker 2

Right, That would be completely useless in a real dog fight, exactly.

Speaker 1

I mean, they practice against red teams, and these are highly trained squadrons whose entire operational purpose is to simulate the exact maneuvers, the communication styles, and really the aggressive mindset of enemy nations because the.

Speaker 2

Core philosophy there is incredibly simple. You cannot properly defend yourself from a threat if you don't intimately understand.

Speaker 1

It right, and that philosophy is our operational baseline for today. We are taking a deep dive into the modern digital battlefield, trying to reverse engineer the tactics of cyber criminals.

Speaker 2

Yeah, and we're doing that by looking through the lens of ethical hacking frameworks and industry gap assessments.

Speaker 1

So we're getting into the actual mechanics of how the offense operates, so you the listener, can understand why the defense has to think exactly like them.

Speaker 2

Which means, first off, we need to immediately discard the Hollywood mythology of hacking.

Speaker 1

Oh, you mean the lone teenager in a dark room wearing a hoodie.

Speaker 2

Exactly the kid chugging energy drinks and breaking into the Pentagon just for the thrill of it. I mean, that era of the digital joy rider is well, it's essentially.

Speaker 1

Dead, right, So let's unpack that shift. Because if the joy writer is dead, who are the actual enemies currently on this battlefield? That is the big question, because looking at the sheer scale of the attacks we're analyzing today, it sounds less like random vandalism and more like like we are dealing with Fortune five hundred crime syndicates.

Speaker 2

That's a much more accurate framework, though honestly, it might even understate their sophistication.

Speaker 1

Really.

Speaker 2

Yeah, the modern digital underworld is a highly organized, heavily profit driven ecosystem. The monetization strategies are They're incredibly complex. They aren't just stealing credit card numbers in bulk anymore.

Speaker 1

Okay, so what are they doing instead?

Speaker 2

Well, they're actively manipulating global financial markets. Take hack pump and dump schemes for example.

Speaker 1

Okay, so a traditional pump and dump is when someone buys cheap stock, hypes it up with fake news to inflate the price, and then sells it. How does the hacker version of that work.

Speaker 2

The mechanism is much more direct, actually, and it doesn't rely on tricking the public with fake news at all.

Speaker 1

Oh it doesn't.

Speaker 2

No, The hackers compromise online brokerage accounts belonging to everyday victims. Then they use the victim's own money to forcefully buy up massive volumes of worthless penny stocks.

Speaker 1

Wait, they just log in and buy the junk stock using someone else's cash.

Speaker 2

Exactly, And because of that sudden buying pressure, the stock price artificially spikes.

Speaker 1

Oh, I see where this is going, right.

Speaker 2

The hackers, who already quietly bought shares of that penny stock beforehand, sell off their own shares at the inflated peak for a massive profit.

Speaker 1

Wow. So by the time the market corrects itself, the victims accounts are drain and the hackers have just vanished with the cash.

Speaker 2

Yep, it's weaponizing them's own portfolio to alter market dynamics.

Speaker 1

That is a sophisticated financial crime, not a computer prank. And speaking of sophisticated financial crimes, we have to look at the logistics of the Royal Bank of Scotland.

Speaker 2

Heighs oh yeah, they arebs incident. That's a big one.

Speaker 1

I mean, a group walked away with nine point four million dollars in just twelve.

Speaker 2

Hours in physical cash.

Speaker 1

Mind you right, how is that level of physical, real world coordination even possible across twenty one hundred ATMs globally?

Speaker 2

It's basically a masterclass in decentralized logistics. A highly coordinated group primarily Russian, Estonian and Moldovan operators, managed to break the encryption of the bank's payment processor.

Speaker 1

Okay, so they get inside the system.

Speaker 2

Right, But once inside, they didn't just transfer money digitally. They manipulated the database to drastically raise withdrawal limits on a specific set of compromised prepaid debit cards.

Speaker 1

So they essentially removed the ceiling on how much cash those accounts could spit.

Speaker 2

Out exactly, took the limits right off. Then they distributed the decrypted card data to a global network of what they call cashers or mules.

Speaker 1

And these are real people on the ground.

Speaker 2

Real people, physical operatives in dozens of cities worldwide. They had created counterfeit magnetic stripe cards using that stolen data.

Speaker 1

And then they just went to the ATMs.

Speaker 2

At a synchronized time, this entire army of cashers hit twenty one hundred ATMs, simultaneously joining the machines of physical cash before the bank's fraud detection algorithms could even register the anomaly.

Speaker 1

Nine point four million dollars gone in half a day gone. You know, you just can't execute something like that without a massive discipline organizational structure.

Speaker 2

No, you can't.

Speaker 1

But they don't always rely on human operatives, right. They heavily leverage distributed computing, like specifically botnets.

Speaker 2

Oh absolutely, botnets are a huge part of this.

Speaker 1

Yeah, because we see groups like the Russian Business Network pulling tens of millions from City Bank using malware, or the zoo juse botnet infecting three point six million computers.

Speaker 2

Zeus was a nightmare, But what really.

Speaker 1

Struck me was how Zeus managed to breach Amazon's EC two cloud computing service.

Speaker 2

Yet that was a critical escalation in the space. A botnet is essentially a network of compromised machines controlled by a single bot.

Speaker 1

Herder, like a zombie army of computers.

Speaker 2

Right, and historically they infected residential laptops. But when Zeus breached Amazon EC two, they weren't just hijacking some home computer's week processor.

Speaker 1

They were in the cloud.

Speaker 2

They were hijacking enterprise grade, massively scalable cloud infrastructure. They turned Amazon's own processing power against its targets, which is how they caused an estimated one hundred million dollars in fraud in a single year.

Speaker 1

That is insane. And it's not just brute force technical attacks either. It's psychological. The cube face botanet.

Speaker 2

Oh cub face. Yeah, that was entirely based on social engineering.

Speaker 1

Right. They hijacked millions of Facebook and MySpace accounts. They weaponize the trust network.

Speaker 2

Itself because you get a message from a friend, right.

Speaker 1

Yeah, linking to a video, but to watch it, you had to click on a fake video player update.

Speaker 2

And of course the update was the malware payload, which really highlights the fundamental economic advantage of modern cybercrime, the automation of exploitation. Once the malware architecture is built and deployed, the marginal cost of infecting the next million victims is essentially zero.

Speaker 1

It requires literally no additional effort from the attacker, none at all. Okay, let's unpack this. I understand the profit motive, and I see the sophistication of the attacks. But here is what I am really struggling with. What's that If these syndicates are this organized, we really need to understand why it is so remarkably easy for them to penetrate corporate parameters in the first place. Like why is the defense always seemingly on the back foot.

Speaker 2

It comes down to an uncomfortable mathematical reality. Yeah, yeah, it is the massive, almost incomprehensible complexity of modern software. The foundational code that runs our operating systems and enterprise applications is simply too vast for human comprehension.

Speaker 1

Okay, let's look at the sheer scale of that, because the numbers are wild. A basic Linux operating system has roughly two million lines of code, but a Windows operating system can have upwards of forty million lines of code exactly.

Speaker 2

Now, apply the industry standard defect rate to that, which is what even with rigorous quality assurance, good developers mathematically lead between five to fifty bugs per one thousand lines of code.

Speaker 1

Wow. So just doing the basic math on a forty million line os, you are looking at an environment that could harbor over a million bugs.

Speaker 2

A million distinct flaws straight out of the box.

Speaker 1

Straight out of the box.

Speaker 2

I mean.

Speaker 1

I like to think of this as a real estate problem. It's like developers are building these massive, one hundred story skyscrapers, but they are leaving thousands of windows unlocked on every floor simply because the tenants enjoy the breeze.

Speaker 2

It's a compelling analogy, but honestly, it's actually worse than that. How So, it's not just that the tenants enjoy the breeze, it's that the tenants demand the windows remain open so they can do their jobs.

Speaker 1

Oh, I see.

Speaker 2

This brings us to the eternal grinding conflict between security and functionality.

Speaker 1

The mister no dynamic.

Speaker 2

Exactly, The mister no dynamic. Users require seamless functionality. They want to share massive files instantly, They want remote access from their personal devices, and they want integration across dozens of platforms.

Speaker 1

They want it all to just work right.

Speaker 2

But from an engineering standpoint, securing a network inherently means turning off those convenient features, closing those open windows, which nobody wants nobody. This is why chief information security officers are often the most unpopular people in a corporate structure. They get labeled mister no or security nazis, because their entire job is to introduce friction into a system that users want to be frictionless.

Speaker 1

But the financial cost of allowing that frictionless environment is just ruinous when a hack actually happens.

Speaker 2

Oh, absolutely rowinous.

Speaker 1

I mean. Looking at downtime analytics from firms like a Linian, the average cost of a computer network going down is forty two thousand dollars per hour.

Speaker 2

And that's just the average, right.

Speaker 1

It scales drastically depending on the critical nature of the system. If a supply chain management application goes dark, that costs company eleven thousand dollars per minute.

Speaker 2

Per minute, which is precisely why ethical hacking and aggressive vulnerability management exist. Because the software environment is infinitely complex and riddled with a million mathematical holes, you need specialized tools to map those vulnerabilities before the syndicates map them for you. Makes sense, but this introduces a fascinating and often uncomfortable reality regarding the tools of the trade.

Speaker 1

Which is that the tools are entirely dual use. Exactly the exact same software used to secure a network is used to destroy it. It's like a lock pick, I mean a lock pick is just a shaped piece of metal. It is inherently neutral.

Speaker 2

Right, it doesn't have a WORL compass.

Speaker 1

Exactly In the hands of a licensed locksmith who you called because you're locked out of your apartment, it's a life saver. But put that exact same piece of metal in the hands of a burglar, and it's a weapon.

Speaker 2

And that neutrality applies across the entire digital spectrum. Consider password cracking software. Okay, a malicious hacker uses brute force algorithms or massive dictionary attacks to steal user credentials, elevate their privileges, and compromise an entire network. But an ethical IT department deploys that exact same cracking software internally to test their own active directory. It is the only functional way to enforce a strong password policy.

Speaker 1

Because you can't just walk cubicle to cubicle and awkwardly ask your employees to whisper their passwords to you to make sure they aren't using password one, two three exactly.

Speaker 2

That would never work. You have to attack your own infrastructure.

Speaker 1

And because these tools and architectures are inherently neutral, it creates massive legal and ethical gray areas. Huge gray areas take a peer to peer file sharing protocol like BitTorrent. The underlying technology is brilliant for decentralized data transfer.

Speaker 2

It really is.

Speaker 1

And the tracker sites, the indexes like torrent, spy or mina Nova, they don't actually host any files themselves. They don't have stolen movies or proprietary datas sitting on their servers right.

Speaker 2

They just provide a directory that points to files hosted by individual.

Speaker 1

Users, which creates an absolute nightmare for cyber law regarding secondary liability.

Speaker 2

It really does. If you build a window that only looks at a crime, are you complicit in the crime.

Speaker 1

It's a tough question, and we see the same friction and search engine optimization too.

Speaker 2

Oh. SEO is a mine field for this.

Speaker 1

Because the line between legitimate SEO where a company optimizes its metadata to rank higher on Google, and malicious spamdexing or building automated scraper sites that steal content to manipulate search rankings, it's incredibly thin.

Speaker 2

The technological mechanism is essentially identical. It is strictly the intent that defines the crime, but.

Speaker 1

Intent is notoriously difficult to prove, especially when we look at activism.

Speaker 2

That's where things get really complicated.

Speaker 1

Yeah, When political activists launch a distributed denial of service attack ADIDAS against a government website during an election dispute or a geopolitical conflict, it forces a really difficult conversation.

Speaker 2

Because they are essentially flooding a server with so much junk traffic that it.

Speaker 1

Collapses exactly now. To be clear, we are just looking at the source materials breakdown of this. We aren't taking a stance here, but the debate is fascinating. From one perspective. Some argue it's a digital sit in, an act of civil disobedience in the modern public square. But from a strict legal perspective.

Speaker 2

Well, from a strict legal perspective, unauthorized access and intentional disruption of services is a federal cybercrime. Regardless of the ideological motivation behind it.

Speaker 1

It's just a crime on paper.

Speaker 2

The law does not typically recognize a political protest exemption for destroying digital infrastructure. But you are right that it highlights the immense complexity of defending these networks. You aren't just defending against profit driven syndicates. You are defending against ideological actors utilizing the exact same dual use tools.

Speaker 1

Here's where it gets really interesting. Given this threat landscape, the million bugs, the dual use tools, the syndicates, the activists, how do companies actually deploy these lock picks to defend their one hundred story skyscrapers.

Speaker 2

It's a multi layered approach.

Speaker 1

There seem to be two distinct layers to this, actually, vulnerability assessment and penetration testing.

Speaker 2

They are distinct, and confusing them is a very common corporate failure. A vulnerability assessment is fundamentally an automated process. Think of a software scanner probing your network architecture, checking the versions of your software against the known database of flaws.

Speaker 1

So it's essentially a security guard walking down a massive hotel hallway just rattling every single doorknob to see if it's locked, and writing down the room numbers of the open.

Speaker 2

Ones precisely, and at the end it's out a massive, terrifying phone book sized list of potential vulnerabilities.

Speaker 1

So uns helpful though.

Speaker 2

It is, but automation lacks contextual awareness that scanner might flag a low risk internal issue like say an outdated driver on a printer in a locks basement, as a high priority, sending the IT team on a time wasting wild.

Speaker 1

Goose chase, which brings me to my next question. If computers can process data and scan networks millions of times faster than a human, why do companies pay human penetration testers. Doesn't the scanner just find the bugs faster?

Speaker 2

The scanner finds the ocillator bugs faster. What the scanner lacks is human cunning.

Speaker 1

Human cunning.

Speaker 2

Yeah, a vulnerability scanner sees one thousand isolated unlocked windows. A human penetration tester, the ethical hacker, looks at the architecture and realizes that if you climb through low risk window A, it gives you just enough access to reach the fire escape, which allows you to bypass the firewall and access the ventilation shaft which drops you to directly

into the domain. Controller. Penetration testing is the act of chaining seemingly boring low level vulnerabilities into one massive catastrophic attack.

Speaker 1

So it's establishing the real world risk exactly. And the methodology for this is highly structured, isn't it. You have the red teams acting as the aggressive attackers and white teams setting the rules of engagement.

Speaker 2

Right. They establish the boundaries first, and.

Speaker 1

Then they passively and actively scan the target. They fingerprint the operating systems by analyzing how the servers respond to specific packets, so they know exactly what architecture they're dealing.

Speaker 2

With yep mapping the territory, and.

Speaker 1

Then they execute privileged escalation. They start as a low level guest user and systematically trick the system until they have administrative control. But the most fascinating part of this dynamic to me is trophy hunting.

Speaker 2

Ah trophy hunting. That is a psychological mechanism used to bridge the gap between technical reality and executive complacency.

Speaker 1

Because executives don't always listen to the.

Speaker 2

IT folks exactly. A security professional can stand in a boardroom and talk to a CEO all day about misconfigured ports, buffer overflows, and protocol flaws, and the CEO's eyes will just glaze over. It's too abstract, right.

Speaker 1

It doesn't feel like a business problem until it physically hurts exactly. Yeah.

Speaker 2

So the ethical hackers deliberately extract a trophy during the pen test to make the invisible threat undeniable, Like what kind of trophy they might exultrate the company's proprietary R and D data or the secret recipe for their flagship product or incredibly effectively, they present the CEO's actual password to the board.

Speaker 1

Oh miss.

Speaker 2

Yeah. When an executive realizes that a hacker just bypassed a million dollar firewall because a VP used I am wearing panties as a password, the abstract technical issue immediately becomes a boardroom priority.

Speaker 1

I bet it does? It forces action?

Speaker 2

Yeah.

Speaker 1

Now, what's really chilling is that the unethical, malicious syndicates use this exact same methodology standing fingerprinting privileged escalation. But their post breach behavior is where the tree true insidiousness shows.

Speaker 2

Oh. Absolutely.

Speaker 1

They don't just take a trophy and leave. They dig in.

Speaker 2

Yes, the persistence mechanisms are deeply complex. They will route their connections through multiple compromised intermediaries, bouncing from a server in Brazil to a router in Ukraine to obscure their origin.

Speaker 1

Just bouncing all over the globe.

Speaker 2

Right, and more importantly, they deploy rude kits.

Speaker 1

Now, a root kit isn't just a standard virus, right, How does it actually hide from the antivirus software that is actively looking for it.

Speaker 2

It's a matter of hierarchy. A root kit embeds itself deep within the operating system's kernel, essentially sitting below the antivirus software. Yeah. When the antivirus asks the operating system, hey, are there any malicious files in this directory? The root kit intercepts that request and forces the operating system to lie and say nope, everything is clean. Wow. It subverts

the very tools designed to detect it. They also meticulously scrub the audit logs to erase any digital food prints of their entry.

Speaker 1

And then there's the ultimate irony, the hostile monopoly.

Speaker 2

Oh, this is fascinating.

Speaker 1

Once a malicious group compromises a server, they will often harden the system like they will actually patched the vulnerabilities they exploited to get.

Speaker 2

In, not out of the goodness of their hearts, of course, no.

Speaker 1

To lock out rival hacking syndicates. They basically become the aggressive it support for the system they just hijacked, so they maintain exclusive control over their stolen real estate.

Speaker 2

Which perfectly illustrates why defensive strategies are so difficult. You are fighting an adversary that understands your infrastructure better than you do and who is highly motivated to protect their illicit investments.

Speaker 1

It's a nightmare scenario.

Speaker 2

It is, but inevitably technical defenses will fail, breaches will occur, and when the digital perimeter collopses, the physical world has to step in to establish accountability.

Speaker 1

So what does this all mean, which brings us to the collision of Internet packets and the physical courtroom.

Speaker 3

Law.

Speaker 2

Yes, the legal battlefield.

Speaker 1

And the stakes here are evolving rapidly because business leaders are increasingly facing personal liability, regulatory fines, and shareholder lawsuits for failing to secure user data.

Speaker 3

It's getting very real for executives when we look at the legal framework in the United States, A massive pillar of this is eighteen USC twenty twenty nine, commonly known as the Access Device Statute.

Speaker 2

It is the foundational text for prosecuting digital financial crimes, but the nomenclature is deceiving. The term access device makes it sound like a physical key card or a hardware token, right.

Speaker 1

It sounds tangible, But how broad is the actual legal definition?

Speaker 2

Incredibly broad. Under the statute, an access device is any card plate code, account number, personal identification number, or telecom service identifier that can be used to obtain money, goods, or services.

Speaker 1

So a string of texts a password is legally an access device.

Speaker 2

Yes, a credit card number sitting in a database is an access device. The federal law criminalizes the production, use, or trafficking of counterfeit or unauthorized access devices.

Speaker 1

And the real world applications of the statute read like scripts from heist movies, bridging that gap between digital data and physical hardware, they really do. We've seen syndicates deploying Bulgarian operatives to Atlanta who were ultimately sentenced to federal prison for ATM skimming. They were physically attaching overlay devices to ATMs to read the magnetic stripes, paired with hidden pinhole cameras to record the keystrokes.

Speaker 2

We've also seen insider threats like rings of waiters in major cities using handheld skimming devices to swipe patron's credit cards before returning them, stealing hundreds of thousands of dollars over months.

Speaker 1

And now the hardware evolution is removing the need for physical retrieval altogether. Hackers are breaking open the housings of gas station pumps, installing wireless skimmers deep inside the machinery, and stealing the pin ins and card data remotely via Bluetooth.

Speaker 2

They never even have to return to the scene of the crime to collect their harvest.

Speaker 1

That is wild, and the pedal to use for these crimes under the statute are designed to be devastating. Fines can range from ten thousand to fifty thousand dollars or up to twice the financial value of the crime itself. Prison sentences for trafficking these devices can easily stretch from ten to twenty years.

Speaker 2

The legal system is casting a very wide, very heavy net to create a deterrent effect, but de terns only works if the law can catch the innovator.

Speaker 1

Which brings up a fundamental paradox I look at the mutation rate of malware. The source mentioned that at one point, security firms like Symantec reported having to write a new virus signature every eight seconds just to keep up with the influx of new threats. Every eight seconds.

Speaker 2

Yeah, that's driven by automated polymorphism.

Speaker 1

What does that mean?

Speaker 2

The malware is programmed to constantly rewrite its own underlying code while maintaining its malicious function. It changes its digital signature every time it replicates, so standard antivirus software, which looks for known signatures, can't recognize it exactly.

Speaker 1

So if the digital threat is shape shifting its own architecture every eight seconds, through automation. How can a sluggish physical legal system, where debating, drafting, and passing a single piece of legislation can take years ever possibly keep up.

Speaker 2

It can't, and that is the harsh reality of cyber law. The legal system is inherently and fundamentally reactive. It observes what has happened, argues about the damage, and tries to penalize it after.

Speaker 1

The fact, while technology just keeps racing ahead.

Speaker 2

Technology is proactive and exponential. This asymmetry is exactly why the security industry relies so heavily on continuous vulnerability assessments and the ethical hacking frameworks we've been discussing. The defense has to operate at the speed of the attack, not the speed of the courts.

Speaker 1

That makes total sense.

Speaker 2

Relying on the law to protect your network is like relying on a homicide detective to prevent a murder. They only show up after the damage is done.

Speaker 1

Wow, it really reframes the entire concept of security.

Speaker 2

Well, we've mapped out quite a journey today for you. We started by discarding the hoodie myth, exposing the global profit driven syndicates manipulating markets and coordinating massive ATM heists.

Speaker 1

We looked at the terrifying mathematics of software complexity too, where millions of lines of code guarantee a porous perimeter.

Speaker 2

We explored the dual use nature of the lock picks and how human cunning is required to chain those vulnerabilities together to break into the boardroom. And finally, we looked at the sluggish, reactive nature of the legal system trying to govern a landscape that mutates every eight seconds.

Speaker 1

It really reinforces the core philosophy you have to understand the offense to build a functional defense.

Speaker 2

And looking to the horizon, the stakes of that defense are moving far beyond financial fraud. The gap between digital code and physical consequence is closing.

Speaker 1

It is we've seen instances where actors use cheap, commercially available software to intercept the live classified video feeds from military predator drones.

Speaker 2

Which is terrifying on its own, but more concerningly, malware is increasingly targeting SKATA systems.

Speaker 1

SCATA being the operational technology that bridges the gap between software and physical infrastructure.

Speaker 2

Right supervisory control and data acquisition. It's the code that tells the physical valves at a water treatment plant to open, or the centrifuges at a nuclear facility to spin, or the switches on a regional power grid to flip. The software is literally integrating into the physical mechanisms of society.

Speaker 1

So the blast radius of a breach goes from a stolen credit card to a compromised municipal water supply exactly.

Speaker 2

So I'll leave you with this to consider. As our physical infrastructure grows exponentially more reliant on millions of lines of inherently flawed code, will we eventually reach a point where these systems are legally and functionally too complex to secure?

Speaker 1

That's a heavy thought.

Speaker 2

Will you, as a digital citizen in a hyper connected society, have to simply accept a baseline level of continuous, invisible compromise as the unalterable cost of living in the modern world.

Speaker 1

It makes you look at every piece of technology around you and wonder just how many windows have been left wide open. Keep questioning the systems you rely on every day. We'll see you next time for our next deep dive.

Transcript source: Provided by creator in RSS feed: download file
For the best experience, listen in Metacast app for iOS or Android