Skip to content

Instantly share code, notes, and snippets.

@sametsazak

sametsazak/Lainons

Created February 10, 2017 22:22
Show Gist options
  • Save sametsazak/8d1ddb9b6a6ca52b331f482cc3f3a81c to your computer and use it in GitHub Desktop.
Save sametsazak/8d1ddb9b6a6ca52b331f482cc3f3a81c to your computer and use it in GitHub Desktop.
Download ZIP
Lainons Pastes
Raw
Lainons
BIOS strong passwords, and strong login passwords, and full disk encryption for physical attacks,
close unused ports and services for things you don't need (not so much a problem for desktops, but still) and keep everything up to date
if you are not using a piece of software (java, adobe flash and other common attack client side vectors) uninstall, and keep your attack surface low as possible
To avoid social engineering don't click attachments on emails or links. Senders can easily be spoofed with tools like SET, If you don't know and need to click, create a vm with snapshots to be safe.
if your browsing shady sites use a vm, for worst case scenario and always keep external backups in a safe location.
Location security, such as needing anonymity while not always need. vpn's and TOR or TOR like substitutes can be used, but make sure you check for leakage because it can happen. Also check vpn companies policy most say they don't check logs, but keep in mind they can start at anytime.
at the end of the day, there is so such thing as 100% security, it's all about getting it to acceptable range or, as low as reasonably possible.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment