Skip to main content

Cancer

Looking at a picture of my mother laying in her hospital chair taking her chemo medication makes me think about cyber. Our bodies are a network of connected computers. Blood and lymph are the communication channels that relay information between these computers. The mainframe, of course, is your brain, which is another highly connected network of computers.

When cancer invades it starts by infiltrating a system. The system is homomophic usually, which makes it easier for the cancer (cyber infiltrator) to gain its foothold. Sometimes the infiltrator moves fast and runs through multiple systems wrecking havoc. Yet there are those infiltrators who move slow, learning each system as it goes slowly through the entire system. Nonhodgkins Lymphoma is that slow hacker. That's what my mother has. She's had this for a very long time. Mostly ignored by her "doctors" 8, 12, maybe 30 years ago, finally they see the infiltration and recognize the need to respond.

Once the cancer becomes apparent, like the infiltrator, we struggle to figure out where it started. That's where we need to address the treatment otherwise we just move it around. That sounds exactly like the cat and mouse chase of counter infiltration. How do we backtrack?

None of the medical "doctors" who work on my mother are savvy enough to even think about this concept. They are mostly preoccupied with billing medicare and collecting their fee for their time. The nurses care, but they're so overwhelmed (like those network techs) that they don't have time to think deeply. Who can stomach a deep dive on the root cause when your system is about the suffer a catastrophic failure, right? Dead humans make for bad test subjects.

Let's work backwards from the visible evidence of infiltration. We see the "cancer" tumor which is the equivalent of a malware drop or data erase, or even a damn DNS exfil that the Cisco guy described. How the infiltrator get into that zone? We look at the path you would take, follow the network, the connected lymp tissue and where it could stage. Look for a similar exploit in that staging area and then again, backtrack. Like a worthy infiltrator, you eventually find rings of exploit that lead back to themselves. That's the frustrating part, and it's the part where most just stop looking. There's always a trail, often some escape that transcends the homomorphic nature of the system.

So you jump across system barriers too. Instead of on a Windows system, you look into the Linux network that has a physical separation (maybe it was your IB HPC network). This is akin to looking into the circulatory system (blood) where it intersects with the lymphatic system, i.e. the liver. The liver would be another computing system with an embedded switch. You look for signs of collateral infiltration, for instance signs of renal cancer (she had that a few years ago).

In all of this backtracking you keep looking for the infiltrator. There is a fingerprint out there, there is always a fingerprint. No matter if it's cancer or a hacker, each infiltrator leaves its mark where it started. Not even the most fantastic NSA red team hacker is immune to leaving a trace. Not every trace is measured in the system they infiltrator.

I am a firm believer that most cancers are the result of viral infection that goes unstopped by an immune system. Sometimes that IPS doesn't know how to handle the foreign "zero day" known as cancer. Maybe one day I will be able to reconnect with Travis, the virology cohort I knew during my SERS experience.

Until then, somebody still needs to collect on the $100 challenge. How many neutrons does it take to make a black hole? My hundo awaits...

Popular posts from this blog

Number of Primes

Anderson's Theorem (a) The number of primes in [1,n] is no more than 2+floor(n/2). The probability of n being prime when n is not prime is 1/2 - see Dasgupta,Papadimitriou,Vazirani "Algorithms" page 26. Therefore, the E(pi(n)) is n/2. (b) There does not exist another set of adjacent primes other than {1,2,3} 5: 2 + floor(5/2) = 2 + 2 = 4:=> {1,2,3,5} : 4 <= 4 7: 2 + floor(7/2) = 2 + 3 = 5 => {1,2,3,5,7} : 5 <= 5 11: 2 + floor(11/2) = 2 + 5 = 7 => {1,2,3,5,7,11} 6 <= 7 26: 2 + floor(26/2) = 15 => {1,2,3,5,7,11,13,17,19,23} : 10 <= 15 Lagrange's Theorem is Inaccurate Lagrange's theorem about primes states that pi(x) is the number of primes <= x. The pi(x) is approximately x/ln(x). He postulated that the lim of pi(x)/(x/lnx) as x-> infinity was 1. This is incorrect. if the number of primes is bounded by n/2 then refactoring and reducing Lagrange's Theorem results in the lim of ln(x) as x approaches infinity. This is alwa...

How To Cancel ATT Uverse

I was a subscriber to the AT&T Uverse service for a little over 2 years. In that time, we had experienced good service for the first year, and then it sucked. After 12 months, or there in, the service degraded quickly, and would stop working all together at times. At first it would die for a short period of time, usually when we were not home. Then it would get progressively worst, until there was an entire week of no service. We had technicians at the house trying to fix the service, but it would repeat the behavior quite consistently. On January 15th we finally gave up and switched to a lesser service, COX TV and Internet. In the past we had cable service and it was always reliable, but not as good as the AT&T digital service. COX doesn't have nearly as many HD channels, but that's not enough. We needed internet to be reliable, and AT&T couldn't deliver that. Cancelling the AT&T service was a nightmare. Try to find anything about such things on their web s...

DNS Custom Logs and selinux

If you google "named custom logs selinux" you will find quite a bit of chatter about setting up custom logs outside of /var/log for DNS (named). These posts are interesting, but they tend to be run on posts about learning selinux and becoming an expert on named. What you need to know? If you have setup custom logging locations in your /etc/named.conf file, such as:     channel default_file {         file "/var/log/named/default.log" versions 3 size 5m;         severity dynamic;         print-time yes;     }; Then you will likely see errors like this in /var/log/messages: Oct 26 11:41:13 namedsvr setroubleshoot: SELinux is preventing /usr/sbin/named from write access on the directory /var/named/chroot/var/log/named. For complete SELinux messages. run sealert -l 6eab4aaf-e615-4ade-9e88-4efdc789eaf2 Then you run the sealert command as suggested by the very friendly selinux audit log and yo...