ISC EDUCATION WEBINAR. Physical Security Information Management

Transcription

1 ISC EDUCATION WEBINAR Physical Security Information

2 PSIM Definition A Physical Security Information (PSIM) system is a software platform with the following components that enhances event management and security operation: Data Aggregation Visualization System & Communication Task Automation Incident Response Workflow Advanced System Reporting 2 Physical Security Information December 15, 2009

3 Why is Integration Important? Reduce Costs Mitigate Risk Increase Compliance 9 Integration Levels Physical Security Information December 15, 2009

4 Three Key Components of Integration When deployed properly, PSIM integration will enable opportunities to optimize business policies and procedures that directly affect the profitability of an organization. Connect Leveraging investments in networking infrastructure to efficiently transport data in an open and standard method Share Easily share data and information between disparate systems to enable proper user visibility Optimize Enabling the optimization of business processes and workflow 4 Physical Security Information December 15, 2009

5 Typical Building System Software Architecture Graphics Reporting Mgmt Config User applications Graphics Reporting Mgmt Config Application interface (XML,.NET, Web Services, etc) Advanced access rules Custom interlocks and sequences Field data collection and storage Application Programmer Interface (API) Application logic logic Normalization to a common format / Application interface (XML,.NET, Web Services, etc) HVAC Auto loop tuning Energy PID Custom interlocks and sequences System Field data collection and storage Wiegand SIA Serial Proprietary Field device drivers BACnet LonMark Modbus Proprietary Field devices (various manufacturers) 5 Physical Security Information December 15, 2009

6 The Problem: Disparate Typical buildings and campuses have a wide array of automation systems of various make, model, and vintage with each having similar functions User interface Graphics & Event Graphics Standard Reporting Proprietary Mgmt Advanced rules Custom interlocks and sequences Field data collection and storage Standard Config Application interface (XML,.NET, Web Services, etc) Proprietary Reporting 6 Physical Security Information December 15, 2009

7 Traditional Integration Software Architecture Connect - Integrating these systems together can reduce complexity by establishing a User Interface Master for each connection Many traditional integrating architectures are rigid and fragile A User Interface Master is established for each point-to-point connection Some systems do not talk to others Compounded complexity with more than one system of a type System upgrade or replacement changes can break integrations 7 Physical Security Information December 15, 2009

8 Reference Architecture for Enterprise Integration Back to the beginning Graphics Reporting Mgmt Config Application interface (XML,.NET, Web Services, etc) Advanced rules Custom interlocks and sequences Field data collection and storage Standard Proprietary Standard Proprietary 8 Physical Security Information December 15, 2009

9 Reference Architecture for Enterprise Integration Connect to enable Sharing Reduce the accumulation of complexity over time, standardization of data structures and messages needs to occur. Utilize standards and conventions collected from systems Message format and content normalization 9 Physical Security Information December 15, 2009

10 Reference Architecture for Enterprise Integration Share All communications between subsystems and applications occur through a messaging system. The messages are XML-formatted information packets whose contents are understandable by applications. Message format and content normalization 10 Physical Security Information December 15, 2009

11 Reference Architecture for Enterprise Integration Optimize Application logic can be simplified when it is applied after data normalization enabling optimization of workflow and processes across and business. Rules Configuration Data fusion, application, and workflow rules Data Archive Message format and content normalization 11 Physical Security Information December 15, 2009

12 Reference Architecture for Enterprise Integration Applications from a variety of sources can be applied across the enterprise ID Event Compliance Building Rules Configuration Data fusion, application, and workflow rules Data Archive Message format and content normalization 12 Physical Security Information December 15, 2009

13 A Simplified View Connecting, Sharing, and Optimizing to reduce costs, mitigate risk, and increase compliance 13 Physical Security Information December 15, 2009

14 PSIM Definition A Physical Security Information (PSIM) system is a software platform with the following components that enhances event management and security operation: Data Aggregation Visualization System & Communication Task Automation Incident Response Workflow Advanced System Reporting 14 Physical Security Information December 15, 2009

15 Components of PSIM Data Aggregation Normalizes data from disparate systems to common format Enables sharing of data between systems Stored data can be queried easily ID Event Compliance Building Rules Configuration Data fusion, application, and workflow rules Data Archive Message format and content normalization 15 Physical Security Information December 15, 2009

16 Components of PSIM Visualization Presents important information in easy-to-understand format Enables full situational awareness for Operators ID Event Compliance Building Rules Configuration Data fusion, application, and workflow rules Data Archive Message format and content normalization 16 Physical Security Information December 15, 2009

17 Components of PSIM System & Communication Override connected systems and devices Communicate to other systems/people Dispatch appropriately ID Event Compliance Building Rules Configuration Data fusion, application, and workflow rules Data Archive Message format and content normalization 17 Physical Security Information December 15, 2009

18 Components of PSIM Task Automation Intelligence makes simple manual tasks automatic Configurable logic reduces manpower need for simple tasks ID Event Compliance Building Rules Configuration Data fusion, application, and workflow rules Data Archive Message format and content normalization 18 Physical Security Information December 15, 2009

19 Components of PSIM Incident Response Workflow Guides Operator through logical steps for a proper response Allows for simple step-by-step Operator assessment to a complex incident ID Event Compliance Building Rules Configuration Data fusion, application, and workflow rules Data Archive Message format and content normalization 19 Physical Security Information December 15, 2009

20 Components of PSIM Advanced System Reporting Displays full audit trail of event and response history Answers important security or business related questions ID Event Compliance Building Rules Configuration Data fusion, application, and workflow rules Data Archive Message format and content normalization 20 Physical Security Information December 15, 2009

21 Implementing PSIM Integration 21 Physical Security Information December 15, 2009

22 Challenges in Deploying PSIM Engaging the right stake-holders Defining scope of services Creating of response workflows Identifying all potential incidents Defining proper response to each Finding concrete numbers to support business case Quantifying risk mitigation Finding hidden cost in current approach Harvesting labor savings Estimating financial impact of best practices 22 Physical Security Information December 15, 2009

23 Business Outcomes of Successful PSIM Deployment Reduce Costs Consolidate command centers Reduce guard or operator cost Decrease integration maintenance Mitigate Risks Automate simple Operator tasks Enhance situational awareness during emergencies Maintain continuity of security operations Increase Compliance Optimize Operator responses to incidents Standardize on best practices 23 Physical Security Information December 15, 2009

24 Questions Brandon Arcement Physical Security Information December 15, 2009