Pki smart-card threat detection and endpoint use visibility
AssigneeThales Dis Cpl USA, Inc.
InventorPankaj JOSHI
Life of this patent
Estimating the term…
Abstract
Provided is a Middleware comprising an Event Generator to generate events related to access and usage of the authenticator device by one or more apps executing on an end-point; an Event Viewer that makes visible events related to certificate based PKI authenticator device interactions by the one or more apps; and an Event Uploader to upload the events. An Analytics Engine on a server side identifies an application usage status of the authenticator device in view of event and application correlations, builds analytics on usage patterns from the application usage status on PKI authenticator device interactions by the one or more apps, and reports anomalies and potential attacks on the authenticator device in view of the analytics based on an event threat analysis.
Claims14
A system (100) to detect targeted Public Key Infrastructure (PKI) threats and attacks on an end-point (10) communicatively coupled to an authenticator device (5) providing PKI based Multi-Factor Authentication (MFA), the system comprising:
- on a local side:
- a Middleware (14) connecting one or more Applications (15) to the authenticator device (5) by way of an Operating system (OS)(13) there in between, said Middleware comprising:
- an Event Generator (22) to generate events (50) related to access and usage of the authenticator device (5) by the one or more apps executing on the end-point;
- an Event Viewer (23) that makes visible events related to certificate based PKI authenticator device interactions by the one or more apps;
- and
- an Event Uploader (24) to upload the events;
- on a server side, communicatively coupled to the local side:
- an Event Receiver (31) to receive the events (50) presented by the Event Uploader;
- an Event Parser (32) to parse and categorize the events, from the Event Receiver, specific to each of the one or more apps executing on the end-point;
- an App Inventory Manager (44) coupled to the Event Parser to correlate the events with the one or more apps and keep records of the correlations in a Database (40);
- an Analytics Engine (48), coupled to the Inventory Manager and Database (40), that
- identifies an application useage status of the authenticator device (5) in view of the correlations;
- builds analytics on usage patterns from the application useage status on PKI authenticator device interactions by the one or more apps;
- identifies anamolies and potential atttacks on the authenticator device in view of the analytics and produces an event threat analysis;
- and,
- an Event Viewer (33) that reports event threat analysis, and makes visible to system administrators events related to user and attacker interactions with the authenticator device.
A Middleware (14) on a local side connecting one or more Applications (15) to an authenticator device (5) by way of an Operating system (OS)(13) there in between, said Middleware comprising:
- an Event Generator (22) to generate events (50) related to access and usage of the authenticator device (5) by one or more apps executing on an end-point;
- an Event Viewer (23) that makes visible events related to certificate based PKI authenticator device interactions by the one or more apps;
- and
- an Event Uploader (24) to upload the events, wherein the Event Viewer (23) receives an event report (400) from an Analytics Engine (48) on a server-side that
- correlates the events with the one or more apps and keep records of the correlations in a Database (40) by way of an an App Inventory Manager (44);
- identifies an application useage status of the authenticator device (5) in view of the correlations;
- builds analytics on usage patterns from the application useage status on PKI authenticator device interactions by the one or more apps;
- identifies anamolies and potential atttacks on the authenticator device in view of the analytics and produces an event threat analysis;
- and wherein the Event Viewer (23) presents information from the report (400) to a local user on the local side regarding application level activities associated with the authenticator device.
Dependencies are inferred from the claim text.