Brushbeater: Developing, Exploiting Signals Intelligence

NC Scout at the Brushbeater blog has an article up, Developing and Exploiting Open Source Signals Intelligence, in which he discusses the types of information that you should be collecting now for your data books on local communication capabilities as well as foreign.  A third of Americans expect a civil war in the next five years. If a civil war indeed happens, then it’s likely there will be foreign meddling. It’s easier to find out information about capabilities now than during any hostilities.

IMG_1309…Back in the early days of this blog I wrote short blurbs about the importance of things called Data Books– which should be nothing new for veterans of more elite units out there and for Long Range Marksmen. But Data Books are not limited to recording Data On Previous Engagements (DOPE) on our weapon systems– it should also serve as a quick reference on a large number of topics for us as we operate in an area. Things that really come in handy, such as:

  • Flora and Fauna, both good and hazardous
  • Key Terrain Features, including Human, in the Area of Operations (AO)
    • Local gathering sites
    • Local persons of influence
  • Equipment recognition guide and data cards
  • Technology present in my AO

That last bit is critically important- there’s a reason every Intelligence agency has a technology analysis branch. We have to know what a potential adversary’s capabilities are, beginning with his principle enabler- communications. As I cover in the RTO course, advancements in radio technology being fielded in all areas is changing at a rapid rate. Civilian data in the US is publicly published. Even military data is not terribly hard- the specifics take some digging but glossing over but FCC Frequency Allocations gives a great starting point as to what can be found where. It might be a really good idea, and one I cover in class, to write down all of the license free band frequencies; you know, like the frequencies those MURS, FRS/GMRS, and Marine are actually on? That way if I happen to come across a group talking on 151.82mHz, I know know they’re on MURS 1 and can begin communications mapping of their capabilities.

Wait, what? Communications Mapping is not at all a hard concept- I listen for you, write down where you’re transmitting and a compass bearing (if I can get it) while also writing down any other pertinent information. Things like callsigns, male/female voices, times, languages, accents, emotions, the level of training, and if they’re even hostile from the traffic itself are all items that can tell us the level of organization (or lack thereof) of our adversary. And while it sounds simple, it takes discipline and training to execute correctly and to also remember- you’ll be on the receiving end of this as well

Read the entire article by clicking here.



Sparks31’s TECHINT blog post and his SIGINT class

Sparks31’s Police Scanner Workbook

Brushbeater’s Signals Intelligence Resources

Brushbeater’s SIGINT for the Small Unit

Forward Observer Interview with Sparks 31 on Communications Monitoring

Sparks 31’s Reference Material

Selco: Observe and Prepare for the Confusion, Panic, & Mayhem of SHTF

Brushbeater: Data Books and What Should Be in Them

NC Scout over at the Brushbeater blog has yet another good article up, this one about the importance of data books.

Why Should I Take The Time To Bother With All This? Because, as with everything else, having a handy-dandy back pocket reference to whip out makes recalling critical info easy. If you’re of the mindset that everything as you know it will be the same when you’re shivering, exhausted and afraid, you’re absolutely wrong.

I had a soldier who stepped on a toe popper in Afghanistan. What’s a toe popper? A small IED placed to kill or maim a small group or lone bubba. We were absolutely spent- a 15 mile movement through the mountains, up and down, all night- and boom, he was down. You don’t think at that point, you default to your highest level of training. Time to treat and send up the 9-line…which was the easy part, because it was already laid out. I had not only memorized the 9-line MEDEVAC report on two previous deployments but had written many- and yet I defaulted to the notes. Because I couldn’t think at that point, with the training taking over and the data book filling in that gap.

For our common purpose, there’s a ton of data that could be included that goes far beyond simply what was listed previously (although that stuff is absolutely critical) such as infrastructure information…

Source: Back to Basics: Data Books and What Should Be in Them