Software Forensics: Can We Track Code to its Authors?

Viruses, worms, trojan horses, and crackers all exist and threaten the security of our computer systems. Often, we are aware of an intrusion only after it has occurred. On some occasions, we may have a fragment of code left behind --- used by an adversary to gain access or damage the system. A natural question to ask is "Can we use this remnant of code to positively identify the culprit?" In this paper, we detail some of the features of code remnants that might be analyzed and then used to identify their authors. We further outline some of the difficulties involved in tracing an intruder by analyzing code. We conclude by discussing some future work that needs to be done before this approach can be properly evaluated. We refer to our process as software forensics, similar to medical forensics: we are examining the remains to obtain evidence about the factors involved. 1 Introduction An aspect of both computer crime and computer vandalism that makes them more attractive activities is th..

Cubic silicon carbide implantable neural prosthetic

An implantable neuronal prosthetic and method of manufacture thereof includes at least one elongated electrode shank adapted for arrangement in the brain having at least one electrode contact disposed on its surface and arranged to electrically couple with said brain. The at least one elongated electrode shank is formed form a single crystal cubic silicon carbide. An insulation layer of amorphous, polycrystalline, or single crystal silicon carbide is disposed over the elongated electrode shank; the insulation layer of amorphous, polycrystalline, or single crystal silicon carbide is removed from the at least one electrode contact. Signal control electronics are attached to the at least one elongated electrode shank and are in electrical communication with the at least one electrode contact. In an embodiment, a plurality of the at least one elongated electrode shanks are arranged into a matrix