Hopefully you would have read the introduction into the “Art of Cyberwarfare” series to understand where this is coming from and where it is headed.
With that out of the way, let me dive into “Cyberwarfare Decomposition ... Fail.” From the Intelligence Analysis book: Decomposition: Breaking a thought or activity into basic elements to discern meaning or facilitate a more complete understanding.
Decomposition of a cyberattack is a bloated, misunderstood and fantasy filled science usually with one outcome, wasted resources. In order to understand where I am coming from, I will write this rambling from a hacker's perspective. From an attacker's point of view, I can be whomever I choose to be, whenever I choose to attack you.
Unlike conventional wars, an opponent is usually going to be visible at some point in time. Visible to the extent that intelligence analysts will know whom he or she is. The analyst will know an attacker's weaponry, locations, capabilities and so on.
Someone would have placed a lot of resources in digging up the information. Whether via HUMINT, SIGINT, COMINT, IMINT, ELINT, MASINT, ACINT or whatever other INT I missed, there is some form of tangible/visible data on an opponent.
In the realm of the Internet (cyber realm), you will fail miserably if you think that you can pinpoint an opponent via an IP address or even collection of addresses, a signature, a comment in an application and so forth.
To prove point one of that comment, I recall a discussion years ago on the North American Network Operators Group (NANOG). The thread discussed how the European Union "made IP personal."
As reported in the news: “IP addresses, a string of numbers that identifies a computer, should generally be regarded as personal information, the head of the European Union's group of data privacy regulators said Monday.”  This started a long discussion about how absurd of a statement, theory, thought, notion, etc., the European Union just blurted.
From the NANOG thread:
“Well, let me ask you you think 188.8.131.52 is. I'll give you a hint; at this instant, there are 72 of us.
Here's another question. Whom would you suspect 184.108.40.206 is? At this point in time, I am in Barcelona; if I were home, that would be my address as you would see it, but my address as I would see it would be in 10.32.244.216/29. There might be several hundred people you would see using 220.127.116.11;” 
Imagine for a moment that I compromised a machine on the subnet mentioned in that thread, who would you (after being attacked from that address) investigate or retaliate against if you were in a cyberwar where you had to launch an offensive? This lack of pinpointing an attacker is, and will continue to be, the problem: attribution. Who do you place the blame on.
Furthermore, from the deception level, it makes all the more sense for me as an attacker to utilize the core functions of the Internet (IP) as a means of hiding. “Catch me if you can.” With millions of vulnerable machines worldwide, an attacker can launch an attack from anywhere with almost no attribution. This makes any analysis pretty much useless for the most part, wasted resources.
When security professionals disclose information about "command and control" botnets, they almost always have the information regarding a) what the botnet does b) what it is targeting c) how it is affecting an infrastructure d) where data goes to and where does it comes from. Sometimes an analyst or team of analysts will get a through d or just enough to help them understand what the SOFTWARE was created to do not what the intentions of the author was.
Perhaps the analyst had discovered a rogue program in the wild and the bits of software were reverse engineered to figure out what was being done, maybe someone stumbled upon the software. Fact is that at the end of the day, what have they found as an analyst?
An analyst needs to remember that proper programming of malicious code could leave an analysts with one of two results: false flags or nothing at all. Remember, I wrote “proper programming” meaning that I properly took the time to make myself invisible. I took the time to zero out any identifiable information. Or, perhaps I picked an ally of yours and inserted false flags that point directly to your ally. What then?
When you think about the reality of cyber analysis and the issues surrounding the data in that analysis, even from the reverse engineering perspective, any answers speak for itself: wasted resources.
Think about this for a moment: “so many analysts working on reversing this botnet” it would have one believe that at some point in time, at least “one” developer of a command and control, would be perp walked by now, their identity disclosed, game over. Have you ever wonder why this is not the case?
If you have, then you answered it in similar fashion to mine from my previous article: Cyberwarfare Analysis - You're Doing It Wrong. The attackers are anonymous: fail - you're doing it wrong. NOTE: When I use the term anonymous in my writings, I am not talking about the “hacktivist” group.
From the attacker's perspective I say to the analyst and I repeat: “Catch me if you can.” The likelihood of an analyst coming close to identifying me is the same likelihood that I will win the lottery in multiple states simultaneously. This is of course based on me having a direct plan of attack and exit plan.
Yet to be quite honest, an exit plan is not even necessary thanks to millions around the world, who in their rush to remain online 24/7, make finding a random connection for me to abuse, child's play.
Connectivity (hackers definition): an abundant resource especially in cities which one can fire off anonymous attacks against any target of choice without worry or repercussion. Businesses and individuals are quick to throw up all forms of wireless connections, Internet cafes are abundant and people are outright mindless when it comes to connectivity. You can't fix stupidity which will always be yet another anonymous enemy attacking you. Fact is, stupidity might be your second biggest enemy.
As an attacker, I could say head to Bryant Park in NYC, change my MAC address  and begin karmetasploiting  anyone in the vicinity. I could steal credentials from someone near me and begin hopping in and out of other networks launching attacks with the credentials I stole.
Perhaps log directly into the computer of the victim whose credentials I stole and launch the attacks from there. When all is said and done and my attack is over, simply shut down my laptop, plop out the copy of Backtrack  from my DVD drive and split it into pieces dumping it piecemeal across the city. So much for evidence.
The fix for these types of problems (rampant and redundant connectivity) is not an easy one in fact, there likely is no fix for the foreseeable future. Besides, you can never fix a social problem with technology. “How do you fix stupid?”
Most wireless networking equipment can be configured with stronger encryption and authentication mechanisms (TKIP, WPA2, etc.) however the likelihood of getting someone to fix their network is low. One can state: “We can pass laws to force them to fix this” but how would you enforce them?
Perhaps create the Department of Open Wireless Network Enforcement? “DOWNE” is actually a cool looking acronym, but I do not want my tax dollars spent funding it. I go back and state: “You can't fix stupid.”
From the analytical perspective now, what information have I gathered from an attack? I see an IP, I see an attack. I have nothing more than that. I may infer some form of motive behind the attack, for example: as an engineer analyzing network traffic in a financial institution, I see an IP address performing Cross Site Scripting attack queries on the institution's servers. T
here is a high likelihood that that the attacker is after something specific with the underlying goal usually leading to money. Any percent attributed to this statement would be outright false.
It would not merit any objective number from any scientific study: “the percent of attackers...” Fail. It would be a waste of time. How realistic would a “percent” statement be at the end of the day. What concrete evidence do you have?
Let us have an alternative point of view now, from the systems slash network administration and engineering perspective. How many of you reading this have ever fat fingered an address? If you haven't, then it is likely true that you have not been an engineer or an admin very long.
Imagine that as an engineer you have to diagnose an address of 10.10.10.5 on your network. You quickly type the address into a command line utility as this is an e-commerce server that needed to be online yesterday:-bash2-2.05b$ ping 10.10.1.5
PING 10.10.1.5 (10.10.1.5): 56 data bytes
--- 10.10.1.5 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
# ssh 10.10.1.5
That is definitely not a typo from the writing perspective but it is a typo from the engineering perspective. At no point in time did I mean to type 10.10.1.5 however, I did type just that. Was I attacking this machine? Absolutely not. Now imagine if I had tried to ssh into this machine:
The authenticity of host '10.10.1.5 (10.10.1.5)' can't be established.
RSA key fingerprint is 14:be:bc:ca:ed:1b:64:3d:86:ba:4e:61:44:cd:d2:0a.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '10.10.1.5' (RSA) to the list of known hosts.
Permission denied, please try again.
Permission denied, please try again.
After the denials, I realize the mistake and correct it. From the endpoint perspective (the admins at the address of the typo I made), they have no inkling that what had occurred was human error and not an attack against their systems. Those admins if on a Linux machine will see:
-bash-3.00# tail -n 4 /var/log/secure
Mar 10 09:15:32 bankingmachine sshd: Failed password for innocentmistake from ::ffff:10.10.10.13 port 58374 ssh2
Mar 10 09:15:35 bankingmachine sshd: Failed password for innocentmistake from ::ffff:10.10.10.13 port 58559 ssh2
Mar 10 09:15:38 bankingmachine sshd: Failed password for innocentmistake from ::ffff:10.10.10.13 port 58740 ssh2
Mar 10 09:15:41 bankingmachine sshd: Failed password for innocentmistake from ::ffff:10.10.10.13 port 58919 ssh2
Quite easy for alarms to ring wouldn't you think. However, any investigation into this occurrence would be a waste of time, the solution would be for the bank to block this everything else from reaching SSH and solely allow what needs to be allowed in. The kicker to this bit of common sense is that many networks keep doing it wrong.
With so much documentation on sites like NIST, NSA, SANS and countless other security websites, it is amazing to see how organizations keep failing. Administrators and engineers can and should take an altogether different approach to security.
We as engineers and administrators may never be able to stop random attackers from knocking on our door, we can however stop answering the door. This is another failure from the security management level right on down to the engineering level.
Imagine the following topology:
E-Commerce Server 10.20.30.5
E-mail Server 10.20.30.6
A simple and small network with one E-Commerce Server and an E-Mail server. What is the purpose of the E-Commerce server? To perhaps serve traffic to anyone looking at the webserver. Maybe it is someone who wants to check their account or sign up for a new account. This is all the machine was configured to do.
Should someone from the outside world be connecting to say SSH? No. Can we stop them from connecting to ssh? No. Stop for a moment and think about that statement. Sure you can create a rule to drop or reject them but at no point in time will the connections stop coming in. Don't fool yourself. Can we block them with a myriad of firewall rules? Sure but that would be impractical. How do we defend this machine you ask? How about you stop worrying about who the attacker is, what it is they are doing and worry about your server doing what it was deployed to do.
We know that no one should be connecting via services we are not offering (services meaning applications) yet it would be impractical to create hundreds of thousands of rules. Simplicity is the answer here. Block your own server from ever connecting “to” anyone else on services you are not offering. For example on a Linux box, I could create one all inclusive block to my server from connecting to anyone else via SSH.
Simple. “Hey firewall, my address is 10.20.30.5 and any time I try to send something out of some important port, you need to drop it. Don't allow it to happen.” Imagine that. One rule versus thousands. This rule alongside the block in rule. The approach is altogether different here.
Many on the enterprise scale would cry foul and someone can come back and argue about tunneling through HTTP however, when configured properly, nothing is stopping me as an engineer and or security professional, from taking a look at what MY MACHINES are doing.
My goal is to block my machine from initiating connections outbound on what I have labeled as “important services.” This portion is always under my control, not the connections of others trying to come in the door, they will always keep trying.
In ending this little rambling Richard Bejtlich has written an excellent book on the entire subject: “Extrusion Detection.”  So go back and ask yourself: “why are you worried about who is knocking on your door if you cannot see them,” the whole scenario is out of your control. Furthermore, why even waste your resources in answering that door if by now you know there is no one there?
Besides, even if you did see something, the reality is you will never know who they are anyway. The effort and resources are better spent investigating WHY your machine is initiating connections to the island of Footopia at 3AM. Don't worry too much about what is coming to your door, worry more about what is exiting your house. This is not to say don't ever wonder who is knocking on your door, it is merely to say: “don't stress it that much" you have more important things to worry about.
Cross-posted from Infiltrated