War Texting - iSEC Partners

More documents

Recommendations

Info

Don’t make it harder• Increase crypto usage• Ensure APN security• Use Nonces/Tokens• Don’t embed IP addresses in SMS ;)• Don’t push insecure architecture▫ Require PKI/SSL• Decrease Prices of Security uC▫ Atmel▫ ST
All tools can be downloaded…• https://wartexting.org/• Simple Zoombak Scanner• FindMe HLR/MSC snarfer• WhoIs Caller ID client• Soon to come (end of next week)▫ STM8 Disassembler▫ STM8 Emulator
Page 1 and 2:
War TextingWeaponizing Machine 2 Ma
Page 3 and 4:
whatis iSEC Partners?
Page 5 and 6:
No, really.• Cellular enabled pil
Page 7 and 8:
But, it’s helping people.• Alzh
Page 11 and 12:
Everything will be a computer
Page 13:
I would have owned ATMs, but…
Page 16 and 17:
Attack methods• Firmware Over The
Page 18 and 19:
FOTA• A methodology for▫ Devisi
Page 20:
FOTA Conclusion?
Page 24:
Long Range Baseband Attacks• Bene
Page 30 and 31:
So, what should we do?
Page 32: Find Architectural Commonalities•
Page 35 and 36: The Payload May Be Encrypted• If
Page 37 and 38: How do we extract it?• Use datash
Page 41 and 42: Next, we reverse.
Page 43 and 44: Some light Hardware Hacking?
Page 45 and 46: Revenge (REVerse ENGinEering)• uC
Page 50: Disassembling & Emulating = Easy•
Page 53 and 54: Point of Reverse Engineering?• De
Page 55 and 56: Building a Fingerprint
Page 57 and 58: Why Device Profile?• SMS is Noisy
Page 60 and 61: Quick Example: iPad on AT&T• Prov
Page 62 and 63: Overall Strategy?• Identify targe
Page 64 and 65: Zoombak “Advanced GPS Tracker”
Page 66: Intercept Initial AT Command Set•
Page 70: Zoombak Network Fingerprint• HLR
Page 73: Zoombak Overall Result?
Page 77 and 78: Strategy• Target industry• Doc
Page 81: Embedded Security is Hard.
Page 85: “Even if my collar bones crush or
show all

War Texting - iSEC Partners

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?