Identity Theft Prophylaxis

or… You are going to get screwed, so let’s minimize the repercussions

There are lots of guides on the Internet on how to safeguard your personal information as a means of preventing Identity Theft. This is not one of those guides. That horse has left the barn, and you are well and truly screwed. Between the breaches at Anthem[1], Equifax[2], US Office of Personnel Management[3], Alteryx (Experian contractor)[4], and countless other small companies who haven’t realized or reported being hacked, your personal information is out there. It’s far too late to keep your SSN, job history, medical history, and recent credit reports off of ‘dark web’ information trading sites. If your information hasn’t already been sold for $2, it will be. If you have kids, their information is available for $300[5]. There is nothing you, the US government, or I, can do to stop that. But you’ve got free credit monitoring as a result of a breach, right? Damn near useless, as I’ll explain below.

It sucks. No doubt about it. If there is any comfort to be had, it is that this is not your fault. The way the privacy laws work in the US, there is no way you could have prevented these companies from amassing so much personal data about you. The penalties for having lost control of that information are laughable; therefore, few companies are investing in Security the way you rationally expect them to. Once you’ve let the fallout from that knowledge bomb settle, we can get on to the business of making that information less useful to fraudsters. There are a few common attacks that a fraudster will engage in to make the most of your details:

  1. Applying for credit in your name. This could be credit cards, payday loans, a car, etc.
  2. Altering your existing accounts. By adding new names and addresses to your existing accounts, fraudsters can have duplicate cards issued to them.
  3. Hijack your cell phone account. By intercepting your text messages they can get past Multi-Factor-Authentication that you have on your accounts.
  4. File a tax return in your name. Submit a return with inflated income, but just enough real data to pass the basic checks.

Remember: Your information is out there. The attacks are coming. Do not wait until you are under attack to go on the defensive. Following the instructions below will save you countless hours cleaning up after a successful identity theft!

Attack: Applying for credit in your name
This is by far the easiest, and probably the first thing the fraudster is going to try. They can use your details to apply for credit on-line, safely away from pesky human interaction. They will apply at every company that targets high-risk applicants, because they know those companies already turn a blind eye towards questionable credit histories. This approach increases their chance of success even when the victim has poor credit. They will also target banks where you already have accounts, hoping the bank will fast track the application of an existing customer. Then all the fraudster has to do is wait for the cards in the mail. Well, they won’t be waiting for your cards… They will have a patsy on the hook for that. More on that below.

Defense: Credit freeze and fraud alerts
The nuclear option is to place a “Credit Freeze” at all three major credit reporting companies. This will cost you $30 ($10 at each of the big three); because while it is your information they reserve the right to charge you money for cutting down on the profits they were going to make selling it. I call this the nuclear option because while completely effective at preventing a vendor from doing a ‘hard inquiry’[6] on your credit report, it makes your life more annoying in the future when you want to take out credit in your name. You will have to temporarily remove the freeze whenever you want to buy a car, house, etc; and then remember to put it back. That said, you should definitely launch this nuke.

You can place a freeze by clicking the links, or calling the numbers, below. Personally, I found getting through the process on the websites to be less annoying than going through the automated telephone systems:

Call, or visit the websites, yourself and retain confirmation numbers for your freezes.  Don’t trust ‘an app’ do to it for you.

Whatever you do, save the PINs you set up for the freeze! These PIN numbers will be useful when you need to remove that freeze to apply for credit. Use an encrypted data-store like 1Password. Not only is it useful as encrypted local storage for website passwords, but it can also store free-form notes. It’s perfect for keeping track of things like unlock PINs, and you can sync it with your smart phone so you have that information with you wherever you need it.

But wait, there’s more! You can also put a fraud alert on your credit files. This is free. It is less of a sure thing than going full nuclear if done alone, but it also provides a mechanism by which a company is supposed to contact you before issuing credit in your name. Fraud alerts come in three flavors: 90 day, seven year, and active duty military. The initial 90 day alert can be done with a phone call to one of the above numbers, or via web page. You only need to do this at one agency, and they are responsible for alerting the others. There is no reason not to do this in addition to placing freezes on your reports.

To place a seven year extended alert you need to send a request by postal mail, and include documentation including a copy of your ID and an identity theft report. (Un)Fortunately, just about anyone in the United States can visit identitytheft.gov and file a report thanks to the various breaches I mentioned in the first paragraph. This report can then be used to activate a seven year fraud alert. You can find more information about how to file for the extended fraud, or active military, alert at the links immediately above.

Attack: Alterations to exiting accounts
This attack takes a little more personal effort, because the fraudster needs to convincingly play you on the phone with a support agent. And by more effort, I mean only slightly more than no effort at all, since the attacker is armed with your credit history and whatever else was part of the ‘dox package’ they purchased. Most customer support agents love to get a happy customer, who seems ashamed they don’t remember their account number, and might have to be asked easier verification questions. That kind of customer is much nicer than the screams they have to put up with when the real customer calls in later. The best part about this attack, for the fraudster, is that when they fail a question they make a note to look up that answer and they just call back and get another call center worker. Once the fraudster gets past the security questions, they put a new email address, phone number, postal address, and name on the account. The next day they call and ask for new cards to be mailed to their patsy. They claim the originals were damaged, not stolen, so they don’t trigger the deactivation of the real account holder’s cards. This kind of attack can go undetected until the real customer sees their next statement, especially if the fraudster made their phone number the point of contact for the fraud department’s calls about a sudden change in spending habits.

Defense:
Visit the websites for all your financial institutions and turn on every alert available in the communication preferences. You want to be alerted when your contact information is updated, when new names are added to the account, etc. This is your early-warning system in case a fraudster manages to impersonate you on the phone.

Add verbal passwords to your accounts. You will likely need to call customer service for this, but it is worth the hassle. This is a password you have to give to an agent before they will discuss your account with you. Never use your mother’s maiden name, or your first girlfriend, or anything you’ve ever seen asked in one of those silly social media quizzes. Use something unique for each bank. Use something immediate and random, like the last book you read, or the last store you shopped at; and then store this password in the password manager you are using for your credit freeze PINs.

Have flags put on your account so that changes can only be made in person. This is the most drastic option, and only works if your bank has a local branch. If you can do this, and your bank honors it, it is worth it. It stops fraudsters in their tracks, for this particular type of attack.

Add Multi-Factor-Authentication (MFA) to all your accounts. Multi-factor is typically ‘something you know’ like a password, and ‘something you have’ like a key-fob or cell phone that has an authenticator app or can receive text messages. That way, if an attacker can guess your on-line account passwords from information in your credit history they are still thwarted when they try to get into your on-line banking.

Attack: Hijack your cell phone account.
While it is commendable that many companies have added MFA to customer accounts, the reliance on cell phones and text messages is a dangerous trade-off between security and convenience. An attacker could get your phone number transferred to another phone, or use an SS7[7] hack to route your text messages to them. Too many companies will offer to text you a one time code if you fail security questions, and then the attacker can bypass account passwords and PINs.

Defense:
Call your cellular carrier and have an additional password put on your account. This will prevent changes to your account, including transferring your number to a new phone. I don’t have any easy answers on preventing a SS7 attack; sorry.

Krebs on Security has also posted a fantastic article on defending against number porting attacks.  You can read it here.

Attack: Filing a tax return in your name.
This attack involves the fraudster using the information they have on you to file a fraudulent tax return in your name. In 2015 the state of Minnesota detected a high number of fraudulent tax returns being filed, which led to TurboTax temporarily halting electronic submissions of state returns[8]. It is easy to infer that if there were a large number of fraudulent state returns being filed, there were likely fake federal returns being filed as well. This attack works particularly well because the default mode of operation at the IRS is to process all tax returns as submitted, and then go after fraud when suspected. That worked well enough when the primary concern was people trying to cheat on their own taxes, but it falls flat when a fraudster is submitting fraudulent returns using the information of real people.

Defense:
The IRS issues a PIN you can use to authenticate your electronic filings. It’s not universally available, so you will want to check with them to see if you can get one at the below URL. The bad news is that even if you have a PIN, it only prevents someone else from electronically filing a fraudulent return in your name; they can still send one in by mail.

https://www.irs.gov/identity-theft-fraud-scams/the-identity-protection-pin-ip-pin

To further protect yourself against negative consequences of this type of attack, be sure to keep all records related to your tax filings. While this has always been the recommendation in case of an audit, you now may need them to prove your return was the real one should the IRS come knocking.

The patsy:
Who is this patsy I keep mentioning? This is a person involved in the enterprise of identity theft who is possibly ignorant of the fact that they are involved in a crime. Their involvement frequently starts when they answer an email or on-line ad promising a work-at-home job as a shipping agent or buyer for an international company[9]. The pitch is that they need someone to locally source computers, and other high-ticket items, because that is cheaper than a business account with some vendors. The company says they will issue corporate credit cards that are to be used for the purchases, and then the merchandise is shipped to a different patsy in the fraud chain. If the police investigate the credit card fraud, the person they find is far removed from the person orchestrating the scheme. The patsy’s plausible deniability starts to fall apart when they’ve received a dozen ‘corporate cards’, that don’t have a company name on them, and they only work for a short while before starting to be declined.

Credit monitoring, and why it’s not a cure-all:
This is the participation award given to consumers when their private information walks out the front door. We get this near worthless salve, presented as a cure-all, while we bleed out from the damage caused by companies that face no lasting repercussions for the careless way they handle the information that could ruin our lives. Anthem paid a $115 million dollar fine for their breach[10]. Seems like a lot, but there were 80 million people who had their information stolen. The loss of our data was calculated to be worth $1.44 per person. Doesn’t seem like much now, does it? We’ll see what happens with Equifax, but as far as I am concerned any penalty they can survive is not harsh enough.  As of this update, it looks like Equifax is going to avoid major penalties for their lax security and oversight regarding your precious data[11].

So, what does that measly year of free credit reporting get you? At best, it will let you know after someone has opened a new line of credit in your name. You are still stuck with the work of cleaning that mess up. Credit monitoring doesn’t look for address additions and new cards issued on your accounts, and it certainly doesn’t prevent someone from filing a fraudulent income tax claim in your name. It’s little more than an inexpensive way for companies to look like they care about their customers.

By all means, accept any free credit monitoring you are offered, as long as it doesn’t come with strings like giving up your right to sue, or having it turn into recurring billing when the free period ends.  Just be aware of the limitations so you are not surprised when it fails you.

Hope:
I know this sounds bleak, but following the above guidelines will go a long way towards securing yourself against these types of identity theft. Fraudsters are looking for an easy return on their investment when they buy your data. Every obstacle you throw in their way makes them more likely to scrap their attack on you and move on to the next victim.


[1] https://en.wikipedia.org/wiki/Anthem_medical_data_breach

[2] https://en.wikipedia.org/wiki/Equifax#May%E2%80%93July_2017_data_breach

[3] https://en.wikipedia.org/wiki/Office_of_Personnel_Management_data_breach

[4] https://en.wikipedia.org/wiki/Alteryx#Data_breach

[5] http://money.cnn.com/2018/01/22/technology/infant-data-dark-web-identity-theft/index.html

[6] https://www.nerdwallet.com/blog/finance/credit-report-soft-hard-pull-difference/

[7] https://www.theguardian.com/technology/2016/apr/19/ss7-hack-explained-mobile-phone-vulnerability-snooping-texts-calls

[8] https://www.forbes.com/sites/kellyphillipserb/2015/02/06/minnesota-stops-accepting-returns-filed-with-turbotax-cites-fraud-concerns/#678d6966c4ba

[9] https://postalinspectors.uspis.gov/radDocs/consumer/ReshippingScam.html

[10] https://www.reuters.com/article/us-anthem-cyber-settlement/anthem-to-pay-record-115-million-to-settle-u-s-lawsuits-over-data-breach-idUSKBN19E2ML

[11] https://m.huffpost.com/us/entry/us_5a7814f6e4b06ee97af48f8f?ncid=inblnkushpmg00000009

Installing MacPorts on MacOS “High Sierra”

Update: The official MacPorts installer is out. Go get it! https://www.macports.org/install.php

Another year, another OS X update. I assume you are here because you downloaded the High Sierra GM from Apple, and were disappointed that there isn’t a MacPorts installer yet.  While I am sure they will release it soon, perhaps we can get you over the hump so you can beat up High Sierra before the official drop date.  If you are comfortable compiling software by hand, we should be able to get thru this easy-peasy.

I am doing this on a clean install of High Sierra. If you are attempting an upgrade from any previous version, your process may vary in unexpected ways.  You will want to make sure you’ve downloaded the latest version of Xcode, and you should probably follow the MacPorts uninstall instructions so you have less cruft around that could interfere with the process.  If you have an upgrade issue, please comment here and I’ll do my best to help you out and improve the instructions.

This is my first pass at getting it running.  I’m going to share all my steps.  One or two things I do might be unnecessary, and could be removed later if I refine the process; but I promise I wouldn’t have hit the Publish button if the overall process didn’t work.

 

  1. Install MacOS “High Sierra”
  2. Connect to the internet
  3. Install Xcode 9 from the App Store.
  4. Launch Xcode:
    1. Agree to the license.
    2. Let it install the extra components it says it needs.
    3. Quit xcode.
  5. Open a terminal window:
  6. sudo bash
  7. xcode-select --install
  8. When the pop-up launches, install the command line tools.
  9. cd ~/Desktop
  10. mkdir macports
  11. cd macports
  12. curl -O https://distfiles.macports.org/MacPorts/MacPorts-2.4.1.tar.gz
  13. tar -xzvf MacPorts-2.4.1.tar.gz
  14. cd MacPorts-2.4.1
  15. ./configure --enable-readline
  16. make
  17. make install
  18. echo 'export PATH=/opt/local/bin:/opt/local/sbin:$PATH' >> ~/.profile
  19. source ~/.profile
  20. port -v selfupdate

At this point, you should be ready to start reinstalling your ports! Wee!

After manually installing MacPorts with the above instructions I was able to install subversion and wget, which are my usual two first validation tests.  Subversion alone has a total of 33 dependencies alone, and combined they have 135 dependent packages; which does a pretty good job of verifying MacPorts is working.

Has SecureCRT 8.1.0 got you down?

tl;dr – If you upgraded to SecureCRT 8.1.0 and your sessions are slow, globally change your font in all your sessions.

SecureCRT is hands-down my favorite secure terminal application on OS X, Windows & iOS.  I’ve been using it since early 1998, and I have never found a better tool.  That said…

This past weekend I got around to renewing my license so I could upgrade to SecureCRT 8.1.0.  I even ponied up for a three year license / upgrade plan.

Withing a few minutes of upgrading, I knew something was wrong.  Slow screen scrolling, slow pasting into sessions, absolutely intolerably slow trying to scroll back through my terminal buffer.

It was downright painful.  So painful that I pulled version 8.0.2 out of my trash and ran it side by side.  Tests using slo-mo video mode on my iPhone revealed that the new version was scrolling text at 1/5 of the speed of the old version.  That’s a big steaming pile of no joy.

While I had no crash dumps, or forensic evidence of the issue, I shot off an email to support to let them know about the issue.  I got a prompt reply, as I always do from VanDyke Software.  Support was wonderfully patient with me.  (If you have heard that doctors make the worst patients, then ya gotta figure that DevOps Security types make the worst customers of tech.)  They hadn’t encountered the issue, and weren’t able to reproduce; but the back and forth willingness to keep working at the issue is one of the things that makes VanDyke Software an awesome company.

While trying to document a couple of different permutations of the issue, I stumbled onto the cause.  In doing so, I also realize why the ubergeeks at VanDyke Software were not able to reproduce the issue.  I’ve been running SecureCRT on OS X since version 6.6, and some of my existing session configs were originally created in that version, back in 2010.  Who knows how many bits of my configs are functional, but not optimal.  One of those non-optimal settings was apparently my font.  When I globally changed my font, all my sessions sped up.  But wait, there’s more…  When I then globally changed my font back to the original setting, my sessions were still gloriously fast.  How’s that?  I diffed one of my old session configs against a newly ‘fixed’ config. Despite them both having the same font selected in the GUI they had slightly different font settings in the config.  Something had changed in my font catalog, and while using the original data technically worked there was a noticeable increase in overhead to make it work.  Functional, but not optimal.

If this helped you out, please let me know.