Start here
A Maker Guide to Securing Connected Projects
A survey of the main risks facing connected builds, from weak logins to unpatched firmware, and the everyday habits that make them harder to attack.
Tech Horizons
Everyday security practice for makers and the devices they build.
Start here
A survey of the main risks facing connected builds, from weak logins to unpatched firmware, and the everyday habits that make them harder to attack.
Learn the difference between encrypting data as it travels over a network and encrypting it where it is stored, and when a maker project needs each one.
Why devices need patching, what can go wrong when you update, and how to plan for hardware that no longer receives security fixes from its maker.
How leaked API keys are found and abused, what to do if one escapes, and safer ways for makers to store secrets outside their source code.
Why every account needs its own credential, how password managers make that practical, and where long passphrases fit in for the logins you must remember.
What to think about when a build records people: consent, local law, where footage is stored, how long to keep it and how to signal clearly that it is recording.
How to report a flaw you find in someone else's product with care: what to record, who to contact, how long to wait and how to stay within the law.
How devices check their own software at start-up using signatures and a chain of trust, what trusted hardware adds, and where the protections fall short.
Common tricks used to steal logins and access, from fake emails to phone pretexts, plus simple habits that make these attacks much less likely to work.
A plain comparison of text-message codes, authenticator apps, push prompts and hardware keys, weighing convenience against resistance to phishing and theft.
How shared factory usernames and passwords get abused on routers, cameras and boards, and which settings to change first when you set up new gear.
Related topics