Systems And Methods For Secure Network Interoperability and Management

• US 20110302629A1
• Filed: 01/05/2011
• Published: 12/08/2011
• Est. Priority Date: 01/05/2010
• Status: Abandoned Application

• Current Assignee: Andrea L. Whitson, Dale Carruth, James Michael Teal, Thomas James Alexander Campbell
• Original Assignee: Andrea L. Whitson, Dale Carruth, James Michael Teal, Thomas James Alexander Campbell
• Inventors: Whitson, Andrea L., Teal, James Michael, Carruth, Dale, Campbell, Thomas James Alexander
• Application Number:
  US12/985,332
• Publication Number:
  US 20110302629A1
• Time in Patent Office: Days
• US Class Current: 726/3
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database

Abstract

The invention relates to an interoperability system that provides increased security and data tracking to security intensive applications, such as transportation systems that currently utilize a large number of independent devices and related systems.

Claims

1. An interoperability system provides Roles Based Access Controls (RBAC) for access and control of disparate security devices, spanning multiple vendors, building locations, and remote locations as if they were on a shared local network, but with addition access controls that support the diverse needs and requirements of varied user constituency groups.

2. The system of claim 1, wherein the security devices from multiple vendors are traditionally not networked together on a shared network and RBAC must be employed to ensure that user constituency groups who require access to specific vendor platforms (Hardware Providers and System Integrators) but not other vendor hardware platforms are only granted access to the specific devices and network communications protocols that are appropriate for their prescribed use and those uses are recorded for auditing purposes.

3. The system of claim 1, wherein the security devices from multiple vendors are traditionally not networked together on a shared network and RBAC must be employed to ensure that user constituency groups who require access to specific operational performance data (number of available devices, number of bags/hour, number of passengers per hour, number of bag rescans, etc) can obtain such access without providing access to other data sources or facilities of the endpoint device using network communications protocols that are appropriate for their prescribed use and those uses are recorded for auditing purposes.

4. The system of claim 1, wherein the security devices from multiple vendors are traditionally not networked together on a shared network and RBAC must be employed to ensure that user constituency groups who require access to management features of the devices to control internal counters, set system level date and time, update firmware revisions, update software revisions, and update operating thresholds or algorithms and the like, can obtain such access without providing access to other data sources or facilities of the endpoint device using network communications protocols that are appropriate for their prescribed use and those uses are recorded for auditing purposes.

5. The system of claim 1, wherein security devices that is legacy/non-networkable from multiple vendors are traditionally not available on a shared network, a combination of hardware bridging of PLC or RS-232/RS-422 to secure TCP/IP based communications to provide RBAC must be employed to ensure that user constituency groups who need configuration and operational performance details from said devices can obtain such access without providing access to other data sources or facilities of the endpoint device using network communications protocols that are appropriate for their prescribed use and those uses are recorded for auditing purposes.

10. The system of claim 9, wherein data collected from natively networkable devices of claims 2, 3, and 4 and non-natively networkable devices of claim 5 where data collected and transformed can be reused or repurposed and presented to COTS applications using prevailing standards, enabling standard COTS applications to access information and events that would not have been previously enabled for such access.

14. The system of claim 1 further provides solution for users comprises development of an application programming interface (API) that translates status messages from the legacy and/or proprietary format to a secure and encrypted common format, such as Simple Network Management Protocol;

the encrypted message contains one or more levels of encryption;

the decryption of some parts of a message may require some particular set of actions and additional policy checks before it is actually decrypted by the authorized system.

15. The system of claim 1 further has an ability to manually add new events and associate messages with a historical record of what occurred from sources that may not be mechanical or electronic;

the records can be incorporated in a way that the machine learning system can associate these manually entered events with the original equipment manufacturer (OEM) machine messages and the system interpretation.

16. The system of claim 1, wherein a signature may be set up between machines (where possible) and where not possible (if software cannot be altered on OEM machines to handle signatures and source checking), a central data-cop role can be created for the policy server to ensure an audit trail and add a layer of security.

6. An interoperability system provides a unified view of data collected from disparate sources. The software will use a combination of traditional middleware tools functionality and proprietary transformations to enable the data that support multiple “

business objects”

such as passengers, bags, and cargo being processed for transportation to be collected from the disparate sources including different vendor devices and platforms, into a homogenous Common Object Data Model where existing industry standards do not exist.

7. The system of claim 6 above, wherein vendor devices are capable of a networked connection and data supporting multiple business objects must be collected and transformed to support the needs of the varied user constituency in a secure and auditable manner.

8. The system of claim 6 above, wherein vendor devices are not natively capable of a networked connection and data supporting one or more business objects must be collected and transformed to support the needs of the varied user constituency in a secure and auditable manner.

9. An interoperability system provides access to collected information using tools known in the art of ITAM (IT Asset Management) and Network Operations. Data collected and transformed into the common data object model may have alternative uses in Commercial-Off-The-Shelf (COTS) applications that leverage prevailing network management standards like SNMP.

11. The interoperability system having implementing complex event processing capabilities to enable additional operational and security analysis.

12. A system of claim 11 above, wherein data of disparate types or sources (Staff Schedule, User Logins, Login Failures, Multiple Location logins, Building Access Controls, System Configuration Changes etc) are used to assess potential threats beyond the scope of a single passenger or parcel passing through the system which is the current scope of the devices and software of the art today.

13. A system of claim 11, wherein data of disparate types or sources can be correlated to external data sources with dynamic links to those sources. In this embodiment, an “

Alert”

may be generated if a staff member is not scheduled to be on shift, has not passed through the access control system, and the UserID has an unsuccessful login attempt. This alert could generate a link to Digital Video Surveillance system, to look at the grouping of cameras in the area of concern at that point in time. In this use case, the security data is collected by the system, but the Survelance system data is not, but a ‘

pathway’

is define to quickly link to the relevant information in that system.