Top Of The List

As you know, because I mentioned it, everything you do within corporate walls is being monitored. They may not necessarily be actively monitored, but there’s a good chance if you do something quirky it’ll ring a few bells in corporate security or wind up on some monthly report. These are good ways to draw attention, and attention is not good.

But, one of the attributes that makes many banks strong also opens up holes in their information defenses. The banking industry has been consolidating recently. Often the newly acquired institutions are more likely to be Velcro’d on to the mother ship then they are to be assimilated. There are many reasons for this, but one of the biggest is the technology cost, in both dollars and human capital, required to reconfigure the entire IT infrastructure each time another chip is added to the stack.

This means that analysts, like yours truly, are forced to navigate through a myriad of differing types of servers and databases to get to the information we need to make business decisions. While this is cumbersome when completing day to day tasks, it makes it easier for someone to run database queries and hide their covert data gathering agendas. One of easiest ways to do this is to have your code reference a macro located on your desktop. When your code finishes, erase the macro and it becomes very, very hard for someone to go back into your query and figure out what it did. They’ll see the macro referenced, but have no idea what its function is. This is akin to reading a novel’s sequel without reading the predecessor. Sure you can generally follow what’s going on, but you’re definitely not getting as much out of the story as you could be.

This morning Mother sent me a partial business name: ‘Pinnacle.’ This company had become involved the Bulgarian extortion scheme. All I knew was that the company’s name started with Pinnacle and it was located in Florida.

Here’s the short version:

Step 1: From database A, pull all records where the first eight characters of the business name were ‘Pinnacle,’ along with some firmographic information. This brought back hundreds of businesses.
Step 2: From database B, pull all business names located in Florida. This brought back thousands upon thousands of businesses.
Step 3: Move the datasets created in Step 1 and 2 into temp space, giving them different names, so they would be automatically deleted when I signed off.
Step 4: Determine which companies are located on both of the datasets. This brought back a handful of companies, six to be exact.
Step 5: Convert this dataset to a comma delimited text file and download it the Recycle Bin on my desktop.
Step 6: Copy the dataset, but rename it when I upload it back to database A.
Step 7: Append a junk dataset, one copied from a coworker’s directory, containing a few thousand records, to the end of it.
Step 8: Download this back to my desktop in the form of a comma delimited text file, renamed to something else of course.
Step 9: From database C, pull all companies that completed a cash advance on their credit cards within the past 12 months.
Step 10: Determine which of these companies matched with the six companies I identified in Step 4. Luckily, there was only one match. Memorize the account number.
Step 11: From database D, pull credit bureau data from the credit card application, but create the search parameters wide enough so that I would capture the one account as well as a lot of other extraneous noise.
Step 12: Move this dataset, in comma delimited text file format, to temp space. Do I even need to say ‘and rename the dataset’ at this point?
Step 13: Import the dataset from temp space into an access database. Sort data by account number, and locate Pinnacle Travel Enterprises by manually scrolling down until the account number is found.
Step 14: Send email on personal BlackBerry to Mother giving, among other things, the name, social security number, home and cell phone numbers, online banking logon ID, and mailing address of the primary card holder.
Step 15: When cleaning up your electronic paper trail, do not just delete your datasets, save over them first with something benign. Then delete them. I'll save my macros for when I really need them.
Step 16: Dial into next conference call and act like nothing happened.

See, pretty easy.

.-. . ... ..- .-.. - ...