DR. PAUL ALBERT CLARK, D.O.
Osteopathic Medicine at Rockville Pike, Bethesda, MD
License number
Maryland 0102202876
Category
Osteopathic Medicine
Type
Hospitalist
License number
Maryland 0102202876
Category
Osteopathic Medicine
Type
Critical Care Medicine
Address
Address
8901 Rockville Pike, Bethesda, MD 20889
Phone
(301) 400-0604
Personal information
See more information about PAUL ALBERT CLARK at radaris.comName
Address
Phone
517 Buena Vista Ave, Salisbury, MD 21804
4705 Broad Brook Dr, Bethesda, MD 20814
507 Main St, Stevensville, MD 21666
4307 51St St, Bladensburg, MD 20710
3323 Belsford Ct, Dundalk, MD 21222
Professional information
See more information about PAUL ALBERT CLARK at trustoria.com
Dr. Paul A Clark, Bethesda MD - DO (Doctor of Osteopathic Medicine)
Dr. Paul A Clark, Bethesda MD - DO (Doctor of Osteopathic Medicine)
Specialties:
Internal Medicine
Address:
8901 Wisconsin Ave, Bethesda 20889
WALTER REED ARMY MEDICAL CENTER DEPARTMENT OF ORTHOPEDIC
6900 Georgia Ave NW, Washington 20307
(202) 782-1898 (Phone), (202) 782-0740 (Fax)
GENERAL SURGERY CLINIC
6900 Georgia Ave NW, Washington 20307
(202) 782-6542 (Phone)
WALTER REED ARMY MEDICAL CENTER DEPARTMENT OF ORTHOPEDIC
6900 Georgia Ave NW, Washington 20307
(202) 782-1898 (Phone), (202) 782-0740 (Fax)
GENERAL SURGERY CLINIC
6900 Georgia Ave NW, Washington 20307
(202) 782-6542 (Phone)
Languages:
English
System For Protecting Computers Via Intelligent Tokens Or Smart Cards
System For Protecting Computers Via Intelligent Tokens Or Smart Cards
US Patent:
5448045, Sep 5, 1995
Filed:
Feb 26, 1993
Appl. No.:
8/023628
Inventors:
Paul C. Clark - Bethesda MD
International Classification:
G06K 500
US Classification:
235382
Abstract:
The possibility of corruption of critical information required in the operation of a computer is reduced by storing the critical information in a device; communicating authorization information between the device and the computer; and causing the device, in response to the authorization information, to enable the computer to read the critical information stored in the device. The device includes a housing, a memory within the housing containing information needed for startup of the host computer, and a communication channel for allowing the memory to be accessed externally of the housing. The device is initialized by storing the critical information in memory on the device, storing authorization information in memory on the device, and configuring a microprocessor in the device to release the critical information to the computer only after completing an authorization routine based on the authorization information.
Intelligent Token Protected System With Network Authentication
Intelligent Token Protected System With Network Authentication
US Patent:
5892902, Apr 6, 1999
Filed:
Sep 5, 1996
Appl. No.:
8/708412
Inventors:
Paul C. Clark - Bethesda MD
International Classification:
G06F 1100
US Classification:
39518701
Abstract:
An intelligent token protected system includes a local host computer, an intelligent token in communication with the local host computer and a remote host computer in communication with the local host computer. The intelligent token interacts with the local host computer to perform a secure boot on the local host computer with minimal user input. Without additional user input, the intelligent token also interacts with the remote host computer to authenticate the local host computer to the remote host computer.
System For Secure Communication Between Domains
System For Secure Communication Between Domains
US Patent:
2002012, Sep 12, 2002
Filed:
Feb 1, 2002
Appl. No.:
10/060310
Inventors:
Paul Clark - Bethesda MD, US
International Classification:
H04L009/00
US Classification:
713/153000, 713/201000
Abstract:
A method of executing secure communications between first and second domains includes a translating data received from a node of the first domain to a target protocol and transmitting the translated data to a bastion host. The translated data may be filtered by the bastion host to block unauthorized transmissions. The data may then be authenticated and transmitted to a node of the second domain for use in an application. In one embodiment, the first domain is an untrusted domain and the second domain is a trusted domain.