Skip to main content

Privacy considerations for home users

In light of the recent new stories regarding the recently signed legislation allowing ISP's to be able to sell your data
http://www.vox.com/new-money/2017/3/29/15107110/republican-isp-data-privacy

Here are a couple ideas and tips about privacy in general.


  • Don't panic - a lot of the info was already being gathered, this isn't that large of a change regarding scope, it's more of a change to who can profit or sell it (which is a shift for sure).

  • Remember a lot of the services you use today already gather your browser, activity, and search info (google, bing, yahoo, facebook, etc.).

  • ISP's haven't implemented this yet, expect to see new terms of service in an upcoming bill, or an email sent to you, etc.
If you would like to take some steps to try to preserve your privacy, here are some ideas and examples:

  • VPN (Virtual Private Network) - this in essence creates an encrypted tunnel between two points on the Internet. One point being your system or home network, and the other being the VPN endpoint device or system. Not all VPN's are created equal, you have little to no visibility to what your VPN provider will do with your data and how they will manage it (yes they can potentially also sell/mine/store/transmit/receive a search warrant). In some cases this may be even "worse" than your ISP.

  • Use a browser plug in to obscure your activity. Depending on the type of browser plug in, it can encrypt your traffic, obscure it, or generate a lot of meaningless traffic with the intent of obscuring your actual traffic.   

  • Use file level encryption (such as PGP) for encrypting stand alone files that you transmit across the Internet. Be sure to manage your keys appropriately (never share your private key, and store it safely).



 I don't see much of a specific risk at this point, I will continue to encrypt sensitive documents (mostly using PGP) and anything I send across the internet that I don't want casual eyes looking at. Browser history I think is probably already exposed thanks to Google, etc. so I don't think this changes much, except who is/can sell your info. I will use VPNs for work activity (already have) but that's probably it.



Additional links and tool options

VPN references:


  • http://lifehacker.com/5940565/why-you-should-start-using-a-vpn-and-how-to-choose-the-best-one-for-your-needs
  • https://arstechnica.com/security/2016/06/aiming-for-anonymity-ars-assesses-the-state-of-vpns-in-2016/
VPN providers:

https://www.privateinternetaccess.com/pages/network/



Browser plug-ins:

https://cs.nyu.edu/trackmenot/

Comments

Post a Comment

Popular posts from this blog

Requirements for Information Security

If you want to get into Information Security you HAVE to be a/have this skill... Why this is total BS. Almost daily I see someone posting on twitter, trying to be helpful to folks who are looking to get into InfoSec. Often I see "If you want to be in Information Security (Cyber Security) then you HAVE to be a programmer" or "If you want to be successful you have to be a hacker/have a criminal record/have abused systems without permission" etc. While having technical capabilities (such as programming) and having the ability to compromise a system shows a specific skillset neither are required. When talking to people who are interested in Information Security I often refer to it as a cake, there are tons of slices, many flavors, many pieces and parts you can sample, choose to focus on, will be expected to know something about, etc. Incident Response and Forensics (my current focus) is not the only part of Information Security, and certainly not the only part tha...
Post a Comment
Read more

New year, New Vulnerabilities, Old problem...

Happy New Year to everyone! May 2018 provide you with interesting problems and the patience to solve them :) On to the recent kerfuffle about the Intel processor bugs. These vulnerabilities were identified in early January by Google  (original Google security post)  CVE-2017-5715   CVE-2017-5753 CVE-2017-5754 These vulnerabilities have been named "Spectre" and "Meltdown" and are causing a certain amount of anxiety in some environments.  IBM has produced an excellent write up of the vulnerabilities and includes information about the impacts and includes the CVE ratings: https://exchange.xforce.ibmcloud.com/collection/c422fb7c4f08a679812cf1190db15441 Of course new vulnerabilities are bad, and often require work and remediation, but this should be part of your environment's standard vulnerability assessment and remediation program. It's not sufficient to just apply patches from a single vendor (e.g. Microsoft) on a monthly basis and conside...
Post a Comment
Read more