Search

Ajith Kumar Phones & Addresses

  • 12619 176Th Pl NE, Redmond, WA 98052
  • 2515 4Th St, Seattle, WA 98121 (206) 257-4399
  • 210 Wall St #1213, Seattle, WA 98121
  • 10011 NE 1St St #507, Bellevue, WA 98004
  • W Lafayette, IN
  • West Lafayette, IN

Professional Records

Medicine Doctors

Ajith Kumar Photo 1

Ajith G. Kumar

View page
Specialties:
Cardiovascular Disease
Work:
Westover Cardiology
2700 Silverside Rd STE 3A, Wilmington, DE 19810
(302) 482-2035 (phone), (302) 482-2587 (fax)
Education:
Medical School
Washington University School of Medicine
Graduated: 1986
Procedures:
Angioplasty
Cardioversion
Echocardiogram
Cardiac Catheterization
Cardiac Stress Test
Continuous EKG
Electrocardiogram (EKG or ECG)
Pacemaker and Defibrillator Procedures
Conditions:
Acute Myocardial Infarction (AMI)
Mitral Valvular Disease
Acute Renal Failure
Acute Sinusitis
Acute Upper Respiratory Tract Infections
Languages:
English
Description:
Dr. Kumar graduated from the Washington University School of Medicine in 1986. He works in Wilmington, DE and specializes in Cardiovascular Disease. Dr. Kumar is affiliated with Christiana Hospital and Saint Francis Healthcare.
Ajith Kumar Photo 2

Ajith J. Kumar

View page
Specialties:
Internal Medicine, Nephrology
Work:
Kidney & Hypertension Clinic
2124 12 Ave, Lewiston, ID 83501
(208) 743-9986 (phone), (208) 743-1318 (fax)

Lewis Clark Kidney Center
2116 12 Ave, Lewiston, ID 83501
(208) 743-0662 (phone), (208) 743-0677 (fax)
Education:
Medical School
Mysore Med Coll, Rajiv Gandhi Univ Hlth Sci, Mysore, Karnataka, India
Graduated: 1991
Procedures:
Dialysis Procedures
Conditions:
Acute Renal Failure
Acute Sinusitis
Anemia
Atrial Fibrillation and Atrial Flutter
Calculus of the Urinary System
Languages:
English
Description:
Dr. Kumar graduated from the Mysore Med Coll, Rajiv Gandhi Univ Hlth Sci, Mysore, Karnataka, India in 1991. He works in Lewiston, ID and 1 other location and specializes in Internal Medicine and Nephrology. Dr. Kumar is affiliated with St Joseph Regional Medical Center and Tri-State Memorial Hospital.

License Records

Ajith Gangadhar Kumar

License #:
MT037253T - Expired
Category:
Medicine
Type:
Graduate Medical Trainee

Publications

Us Patents

Identification Of Telemetry Data

View page
US Patent:
20100242094, Sep 23, 2010
Filed:
Mar 17, 2009
Appl. No.:
12/405252
Inventors:
Ahmed S. Hussain - Seattle WA, US
Ajith Kumar - Bellevue WA, US
Catalin D. Sandu - Kirkland WA, US
Alvin Loh - Kirkland WA, US
Sterling M. Reasor - Bellevue WA, US
Santanu Chakraborty - Bellevue WA, US
Joseph L. Faulhaber - Bozeman MT, US
Assignee:
Microsoft Corporation - Redmond WA
International Classification:
G06F 21/00
H04L 9/32
US Classification:
726 4, 726 22
Abstract:
Methods, systems, and computer-readable media are disclosed for identifying telemetry data. A particular method scans a file and compares the file to at least one attribute to be used for telemetry collection. When the file is identified as a telemetry candidate, an offer to submit a sample of the file is sent to a server. A response to the offer is received from the server. If the response to the offer indicates an acceptance, a sample of the file is sent to the server.

Discovering Malicious Input Files And Performing Automatic And Distributed Remediation

View page
US Patent:
20120297488, Nov 22, 2012
Filed:
Jun 16, 2011
Appl. No.:
13/161950
Inventors:
Vishal Kapoor - Seattle WA, US
Jonathan Mark Keller - Redmond WA, US
Ajith Kumar - Seattle WA, US
Adrian M. Marinescu - Sammamish WA, US
Marc E. Seinfeld - Fort Lauderdale FL, US
Anil Francis Thomas - Redmond WA, US
Michael Sean Jarrett - Kirkland WA, US
Joseph J. Johnson - Seattle WA, US
Joseph L. Faulhaber - Bozeman MT, US
Assignee:
MICROSOFT CORPORATION - Redmond WA
International Classification:
G06F 11/00
US Classification:
726 24
Abstract:
The subject disclosure is directed towards detecting malware or possible malware in an input file by allowing the input file to be opened, and by monitoring for one or more behaviors corresponding to the open file that likely indicate malware. Only certain executable files and/or file types opened thereby may be monitored, with various collected event data used for antimalware purposes when improper behavior is observed. Example behaviors include writing of a file to storage, generation of network traffic, injection of a process, running of script, and/or writing system registry data. Telemetry data and/or a sample of the file may be sent to an antimalware service, and malware remediation may be performed. Data (e.g., the collected events) may be distributed to other nodes for use in antimalware detection, e.g., to block execution of a similar file.

Applying Antimalware Logic Without Revealing The Antimalware Logic To Adversaries

View page
US Patent:
20120317644, Dec 13, 2012
Filed:
Jun 9, 2011
Appl. No.:
13/156726
Inventors:
Ajith Kumar - Seattle WA, US
Timothy Jon Fraser - Bethesda MD, US
Adrian M. Marinescu - Sammamish WA, US
Marc E. Seinfeld - Fort Lauderdale FL, US
Anil Francis Thomas - Redmond WA, US
Assignee:
MICROSOFT CORPORATION - Redmond WA
International Classification:
G06F 21/00
US Classification:
726 24
Abstract:
The subject disclosure is directed towards a technology by which antimalware detection logic is maintained and operated at a backend service, with which a customer frontend machine communicates (queries) for purposes of malware detection. In this way, some antimalware techniques are maintained at the backend service rather than revealed to antimalware authors. The backend antimalware detection logic may be based upon feature selection, and may be updated rapidly, in a manner that is faster than malware authors can track. Noise may be added to the results to make it difficult for malware authors to deduce the logic behind the results. The backend may return results indicating malware or not malware, or return inconclusive results. The backend service may also detect probing-related queries that are part of an attempt to deduce the unrevealed antimalware detection logic, with noisy results returned in response and/or other actions taken to foil the attempt.

Selectively Scanning Objects For Infection By Malware

View page
US Patent:
20130086683, Apr 4, 2013
Filed:
Sep 29, 2011
Appl. No.:
13/248867
Inventors:
Anil Francis Thomas - Redmond WA, US
Adrian M. Marinescu - Sammamish WA, US
Ajith Kumar - Seattle WA, US
Jonathan M. Keller - Redmond WA, US
Omer Ben Bassat - Redmond WA, US
Assignee:
MICROSOFT CORPORATION - Redmond WA
International Classification:
G06F 21/00
US Classification:
726 24
Abstract:
Techniques are described herein that are capable of selectively scanning objects for infection by malware (i.e., to determine whether one or more of the objects are infected by malware). For instance, metadata that is associated with the objects may be reviewed to determine whether update(s) have been made with regard to the objects since a determination was made that the objects were not infected by malware. An update may involve increasing a number of the objects, modifying one of the objects, etc. Objects that have been updated (e.g., added and/or modified) since the determination may be scanned. Objects that have not been updated since the determination need not necessarily be scanned. For instance, an allowance may be made to perform operations with respect to the objects that have not been updated since the determination without first scanning the objects for infection by malware.

Trusted Installation Of A Software Application

View page
US Patent:
20130185799, Jul 18, 2013
Filed:
Jan 16, 2012
Appl. No.:
13/350816
Inventors:
William Pfeifer - Redmond WA, US
Joseph Johnson - Seattle WA, US
Ronald Thompson - Monroe WA, US
Ajith Kumar - Seattle WA, US
Nitin Sood - Redmond WA, US
Assignee:
Microsoft Corporation - Redmond WA
International Classification:
G06F 21/00
US Classification:
726 24
Abstract:
The trust reputation of the combination of an installation package and installer, as a pair, and the combination of a file and an installer, as a pair, is used to store the identity of a file in a persistent cache. An entry in the persistent cache indicates the trust worthiness of a file that does not contain malware thereby avoiding a scan of the file for malware. The trust worthiness of a file may be determined from known trust reputations of the installation package, installer, and file from a network of computing resources. By relying on the known trust reputation of the combination of the installation package and installer and the combination of the file and installer, the identity of the file may be stored in persistent cache quickly.
Ajith Kumar from Redmond, WA, age ~39 Get Report