Monday, November 4, 2013

No Morsel Too Minuscule for All-Consuming NSA

The New York Times story with the subject line title is here.

The Morsel is the Message!

Located on page 3 is a section titled:  Mapping Message Trails.  That is what caught my attention because that is exactly what the NSA focuses on.  The message, intercepting the message from one entity object address to another entity object address.  Identifying the message content "pay load" in the deep packet and applying keys to it as simple as keywords or as complex as artificial intelligence.

Message transmission "From" and "To" as well as "Info" and other things like Date/Time establishes a meta structure communication framework.  At a time of extreme urgency, this communication intelligence tells who is connected to who when the stuff really hits the fan.  When all the low level planning over time that may not be detectable from normal internet messaging suddenly peaks among key players in what ever the crises of the day is.

The crises of the day might even be one manufactured by the NSA to discover which cockroaches run (communicate) when they concoct a situation that appears to be a real crises of epic proportions to somebody.  Who you gonna call?

The NSA does not "follow" the email any more than an investigator follows the money.  Both email and the money are fixed objects that do not go anywhere.  They only pass messages having attributes and instructions to other external objects.    The message is the action connecting the two objects.  The payload instructions in the message are either educational in nature to teach the receiving object a future behavior that it will perform on request (programming) or causing the receiver to implement the programmed behavior.

Normal object oriented high level system design creates high level object models (OOAD) that have top down tightly binding logically progressing integration to the low level (OOP) object structure to do something as a function of the comprehensive object model design.  The object model "does something" by passing messages among all levels of object classes to invoke their encapsulated behaviors.

The NSA is a business enterprise with a problem domain just like any other business enterprise and uses OOAD and OOP to create an object model to "solve" the problem domain in the most efficient effective manner.  That model is their "in house" enterprise object top down constructed model that structures their resources and command and control in which internal messaging among all internal objects in the system takes place.

The business of the NSA is intelligence.  The discovery of the "enemy's" or "out house"  OOAD and OOP model.  Discovery of the enemy's high level object model and therefore associated user/players through a "reverse engineering process" that focuses not on objects first and foremost as was the case in creating the NSA "in house" object model but focusing on the enemy's messages that encapsulate actions/processes among enemy objects to discover by induction the object model of the enemy through bottom up assembly of actions that relate to objects.

More simply put:  The NSA uses an internally designed "in house" state of the art object design driven model to discover the the "action" process/function driven model of the enemy evident in and displayed by message passing  meta data and internal deep packet content action instructions in the message to create an NSA view of the enemy's object driven model to do whatever solves the problem domain of the enemy enterprise.

The NSA Intelligence model to address its problem domain is the exactly same as the Business Intelligence model to address its problem domain.  Create an object oriented system to discovering the actions of an external entity and by construction of the external entity Process Model reveal their most probable Object Model.  The object model is the business plan that the external entity keeps locked up in the safe.  Knowing the process model is the key to opening the safe to discover the object model.

The NSA model is object design driven.   Primarily a computer machine based internal operating system used by humans to discover the enemy's actions and by association the objects in their problem solving domain.  The enemy, which is the problem domain of the NSA has a human based process oriented operating system design model.

Is the problem domain of the NSA the enemy or security?

What a thing is, the object (real/conceptual tight binding) and what a thing does (real/conceptual loose binding) and which chosen principal approach to the framing the problem also frames the solution.  Historically, they have have been conflicting approaches in not integrated in their essentially pure logic relationship.

Maybe what we have here is the old conflict between John Henry and the Steel Driving Machine.  Who ultimately won that battle between Process and Object?

From the NYT link:

“Our mission,” says the agency’s current five-year plan, which has not been officially scheduled for declassification until 2032, “is to answer questions about threatening activities that others mean to keep hidden.” 

Mission to answer questions about "other's actions?   Or is it a higher level Mission to answer questions about the object oriented design model structure that accomplishes those enemy actions.  Is that strictly in the political domain to answer?  If so it is not going to be answered there because it would indict our object model for ruling the world.

We "rule" the world with an object model.  A process model runs things, dominates things.  An object model rules things and dominates their behavior.

Who provides answers to that question?


No comments: