Guide to Interpreting Security Incident #Announcements:
"extremely sophisticated attack" : The attackers put more time into the attack than we spent designing our defences.
"no evidence customer #data was accessed" : We lack audit records and the logs have been rotated out.
"due to a misconfiguration issue" : We deployed with default #insecure settings.
"possible for only a short window" : We didn't dig too deep to determine how far back the bug existed.
"crafted invalid request data" : We forgot to add input #validation.
"supplementary fix" : We didn't understand the problem as well as we thought, so our previous fix was insufficient.
"may have been exploited" : We're positive they got away with data, but they deleted our #logs.
"multiple threat actors" : Everyone was in our systems before we noticed.
"most customers are unaffected" : There are corner cases that aren't as #vulnerable.
"error in a third-party component" : We forgot to update our dependencies.
"could lead to remote code execution" : You're #p0wned.
"malicious activity has been observed" : The issue has already appeared in the press.
"review equipment inventory to verify if devices require other mitigations" : You need to buy new stuff.
"remotely exploited to allow authentication bypass" : We forgot to require #login for this function.
"not aware of any exploits in the wild" : The attackers aren't bragging on darkweb fora yet.
Check my Image Description’s![Months of work have gone into decoding the Game Boy’s data bus and creating a schematic for the interface board. Tricking the Game Boy into thinking it was loading a game, while actually displaying incoming speed data. The screen’s low resolution and slow refresh rate rendered it barely readable in a moving vehicle. But [John]’s goal wasn’t practicality — it was just proving it could be done.](https://nerdculture.de/system/media_attachments/files/114/251/391/317/762/186/original/f1ea811e6cb4c4c3.jpeg "Months of work have gone into decoding the Game Boy’s data bus and creating a schematic for the interface board. Tricking the Game Boy into thinking it was loading a game, while actually displaying incoming speed data. The screen’s low resolution and slow refresh rate rendered it barely readable in a moving vehicle. But [John]’s goal wasn’t practicality — it was just proving it could be done.")
![[ImageSource: John Sutley]
Showing real-time vehicle speed on the Game Boy sounds like it should be relatively easy, but the iconic game system wasn’t exactly built for such a task. Its 2 MHz CPU and 160×144 pixel dot-matrix screen were every kid’s dream in 1989, but using it as a car dashboard is pushing it. To bridge that gap, [John] designed two custom circuit boards.
One interfaces with the Game Boy, intercepting its memory requests and feeding it data from a microcontroller. The other processes the CAN bus signals, translating speed information into a form the Game Boy can display. [John] used inexpensive tools and software to read the CAN bus data, and used GBDK-2020 to write the software in C.](https://nerdculture.de/system/media_attachments/files/114/251/392/340/955/496/original/f54a186d63357559.png "[ImageSource: John Sutley]
Showing real-time vehicle speed on the Game Boy sounds like it should be relatively easy, but the iconic game system wasn’t exactly built for such a task. Its 2 MHz CPU and 160×144 pixel dot-matrix screen were every kid’s dream in 1989, but using it as a car dashboard is pushing it. To bridge that gap, [John] designed two custom circuit boards.
One interfaces with the Game Boy, intercepting its memory requests and feeding it data from a microcontroller. The other processes the CAN bus signals, translating speed information into a form the Game Boy can display. [John] used inexpensive tools and software to read the CAN bus data, and used GBDK-2020 to write the software in C.")
Materie 
Spiegel
Franky Goes To Matter(n)horn
♬ 
nge? W
