Logo2001



 Commentary> C.U.P.I.D. vs. CIA-NSA-Hackers

With the use of my multi-phase approach to both on-the-fly variable encryption and positive identification of device information, any alphabet agency would be hard pressed to crack any C.U.P.I.D. traffic unless permitted. As dangerous as that claim is - it can be done and all by design.

As discussed in other areas of this website, most malware the CIA and NSA use appear to reside in the slack space of a UEFI BIOS though other locations are available when unannounced exploits are used instead.

To my knowledge BIOS update programs do not write zeros to any unused slack space which means the malware remains. Also, even if a UEFI BIOS slack space were wiped there is no telling where else on your computer/device any core code remains to redownload the malware.

Currently I am unaware of any publicly available software to check for or more importantly, perform the task of wiping any BIOS slack space. If any existed this would delete any hidden malware from not only the CIA or NSA, but also any hackers who have chosen the same route to place their malware on your computer/device.

While BIOS antivirus does exist those too can be forced to whitelist certain code thus exempting it from detection.

Unlike the CIA, NSA and any hacker designs, the C.U.P.I.D. design is able to survive simply because it is not stored in the UEFI BIOS slack space even after a complete BIOS wipe and reinstall. Remember that C.U.P.I.D. is a choice, not hidden, and can be turned on or off from a UEFI BIOS setup option page.

As mentioned in another area of this site, earlier versions of the Intel ME used a on-board chip embedded to the network card to store code awaiting execution by anyone who knew how to access it. Though limited in function, it is highly concerning a stand-alone device like a on-board network card could compromise any internet connectivity without your knowing. As brilliant as Intel Corp. is there are times I scratch my head and go 'What were they thinking???".

While there may be some who think at this point they understand part of the unpatented C.U.P.I.D. design, I can assure you that is not the case as there are several parts to make the whole package function as described throughout this website.

As another nugget to digest, what could be possible with a dynamic version of the current UEFI BIOS slack space exploit? A true double edged sword and powerful indeed. Considering my position on 'Public vs Private', no home-based computer would allow any exploitation without probable cause, thus people have their complete privacy. Only with probable cause and proper legal authority the home-based computer can quietly replicate the exploit (though not from any BIOS slack space) for further investigation. No more spying on people in their homes unless both legal and warranted. Win-win.

 

 

 

 

 

 

 

 

 

 

 

 







Copyright 2017 @www.cupidtechnologies.com All Rights Reserved