taking a look at a random (public) resume of your typical Intel associated “crypto” employee/contractor


October 2006Present (6 years 10 months)

SecureComm, Inc provides consulting services in Software, Security, and Systems, specializing in cryptography and communications.

secureComm is essentially an intel contractor for the design of the crypto component in phones. Note the specialization in layer 3 security association (for connectionless protocol design, suiting CDMA at layer 2).

General Dynamics C4 Systems

October 2006June 2010 (3 years 9 months)

JTRS HMS cryptographic engine design for Type2 radio, including design of hardware random number generation that was NSA certificed, COMSEC and TRANSEC for SRW Waveform; System design for MUOS; worked with SCA/CORBA/C++ on Green Hills Integrity OS, including building device drivers, network protocols, and user interface controls.

General Dynamics purchased GSTG Motorola, who specialized in military radios (and the crypto components). Note the focus on the random number generator. Note also the focus on OTHER than type I waveforms (vs data signals) and the type of crypto that addresses (satellite) waveform transmission. He points out his focus on type 2 (knowing the difference!)

Intel Corporation

June 2003October 2006 (3 years 5 months)

Designed and built a hardware cryptographic engine for Intel’s XScale processor; developed microcode for the HW crypto engine to perform high-level cryptographic functions (e.g. RSA key generation, Digital Signatures, AES-CTR mode, HMAC, etc)

This is similar to the work Spyrus did for NSA, taking the capstone chip and creating a software layer – the responder in the fortezza that that made it act like a PKCS#11 device, addressable using a PKCS#11 driver supporting the likes of cryptoAPI (or intel’s equivalent).

Intel/Mobile Wireless Group

March 2000June 2003 (3 years 4 months) Chandler, Arizona

Designed and developed security software for Intel’s Java-based Network Applicance Server. Performed vulnerability analysis and developed mitigation strategies for attacks on the server. Led four person team to develop Java-based protections for the server.

working in chandler, note, is working at higher level that his traditional forte

FortreSoft, Inc. (Consulting)

February 1998March 2000 (2 years 2 months) Phoenix, Arizona

Consulting in software and systems. Work included systems engineering in communications to Motorola under the Teledesic Satellite project. Additional consulting in web applications (COMPUWARE) and GSSAPI prototype.

GSSAPI plugins and providers, with satellite focus

Touch Technology

Privately Held; 11-50 employees; Information Technology and Services industry

December 1996February 1998 (1 year 3 months)

Designed Smartcard initialization and personnalization system; Integrated smartcard authentication to Oracel Database framework; wrote device drivers for smartcard readers

This guy has ALMOST the same background as I do, the more I read. Note 1996-era focus on smartcards, or the PC (presumably server-class) drivers to smartcard readers, rather

Motorola GSTG

Public Company; 10,001+ employees; MMI; Telecommunications industry

May 1992December 1996 (4 years 8 months)

Wrote Security Association Management Protocol (SAMP), the forerunner Key Management protocol to the ISAKMP.


In this period, GTSG was NSA main contractor for packet-switched encryptors (caneware, etc). Notice the reference to KMP (from the SDNS project). note his previous work on FTAM (see below) – a VERY detailed ISO protocol that demands rather specialized communications knowhow.

Software Engineer

Public Company; 10,001+ employees; HON; Electrical/Electronic Manufacturing industry

19891992 (3 years) Phoenix Arizona

Development of File Transfer, Access & Management (FTAM) application for Open System Interconnect (OSI) communications stack on Unix Systems. Extensive work with ASN.1, C, and Unix communications stack.

This parallels my own work in the same software stack (ISODE) – which had the FTAM responder. This period aligns with when DoD/NSA was pushing FTAM for huge file transfers, that were resumable. By 1992. Likely to be for (then( NSA’s specialized UNIX machines.

Radio Teletype Operator
US Army

Government Agency; 10,001+ employees; Military industry

August 1984October 1988 (4 years 3 months)

2-43 Air Defense Artillery, Hanau FRG

Could mean anything, including he was a “listener” at an NSA outstation in FRG. or, just an comsec custodian… Interesting that he goes from a non-descript army job to VERY SPECIALZED protocol work, above. This is QUITE some jump.

Medical Lab Technologist (Reserves)
US Army

Government Agency; 10,001+ employees; Military industry

June 1982August 1984 (2 years 3 months)


This suggests bio-weapons, or their IT control systems more likely. Total speculation of course.

About home_pw@msn.com

Computer Programmer who often does network administration with focus on security servers. Very strong in Microsoft Azure cloud!
This entry was posted in spying. Bookmark the permalink.