# Unlocking L.A.'s Traffic Grid: Phreaked Out (Episode 1)

{% hint style="info" %}
**2022년 NHN Cloud&#x20;**<mark style="color:red;">**무료**</mark>**&#x20;교육일정** : <https://doc.skill.or.kr/2022-NHN-Cloud-Education>
{% endhint %}

## 제목 : Unlocking L.A.'s Traffic Grid: Phreaked Out (Episode 1)

{% hint style="danger" %}
**주의 : 테스트 이외의 목적으로 발생 되는 문제점에 대해서는 프로그램을 사용하는 사용자가 책임을 지셔야 한다는 것을 알려 드립니다.**

**Disclaimer: I am not responsible for any damage done using this tool. This tool should only be used for educational purposes and for penetration testing.**
{% endhint %}

### 내용 :&#x20;

> IoT 보안을 생각하시는 분들이라면 이런 공격에 대해 생각해 보셔야 할 거 같습니다.

### Description :&#x20;

> In the debut episode of our three-part series titled "Phreaked Out," we took a retrospective look at one day in August of 2006, when two Los Angeles traffic engineers, Kartik Patel and Gabriel Murillo, remotely accessed the city's traffic control system and tampered with the light sequences at four main intersections of the city, as part of a labor union protest.
>
> Although there was little evidence of the attack, their alleged disruptions were reported to have triggered a state of gridlock that lasted days. In 2009, Patel and Murillo copped to the crime, which stood as a reminder that the city of Los Angeles, like countless other metropolises, relies on a certain degree of computerized and internet-connected control systems that are vulnerable to exploitation.

{% embed url="<https://youtu.be/hcoVMXLTQzw>" %}
시연 영상      &#x20;
{% endembed %}

{% hint style="info" %}
**2022년 NHN Cloud&#x20;**<mark style="color:red;">**무료**</mark>**&#x20;교육일정** : <https://doc.skill.or.kr/2022-NHN-Cloud-Education>
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://sec.skill.or.kr/hacking/iot-1-hacking.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.