PCSF extends call for papers deadline

The Process Control Systems Forum (PCSF) 2008 Annual Meeting taking place August 26-28, 2008, in La Jolla, CA, will include a program format that builds upon the highly successful style that was valued by attendees at the PCSF 2007 Annual Meeting. Solution providers are invited to submit requests to present solutions specific to the most pressing issues identified by the control systems community.The call for solutions deadline has been extended until June 2, 2008...

May 19th, 2008

• PCSF 2008 Annual Meeting, August 26-28, 2008, La Jolla, CA; Call for solutions deadline extended until June 2

FALLS CHURCH, VA, May 14, 2008 -- The Process Control Systems Forum (PCSF) 2008 Annual Meeting will include a program format that builds upon the highly successful style that was valued by attendees at the PCSF 2007 Annual Meeting.

End-user involvement in collaborating towards advances in cyber security policy, practices, standards, tools, resources and services is growing steadily. More organizations that work with control systems are discovering the benefits of participating in a dynamic community where the solution seekers and solution providers can exchange knowledge, learn from each other, build a successful cyber security program, and address the high priority, immediate concerns unique to each environment.

Solution providers are invited to submit requests to present solutions specific to the most pressing issues identified by the control systems community. The solution tracks identified at the 2007 Annual Meeting will be utilized as guidance for solution categorization. Feedback gathered from the attendees at the 2007 meeting, specific to updated needs and concerns in each track are also included in the short description.

• Track 1 ~ Understanding Risk
Descriptors: Self Assessment, Threat Identification, Vulnerability Assessment, Vulnerability Awareness
PCSF 2007 Meeting Feedback: Improve the utilization of risk tools; More granular understanding of threat; emphasis upon social engineering and traditional IT vulnerabilities; Uncovering opportunities to improve IT and CS situations through stronger coexistence; Peer to peer assistance

• Track 2 ~ Requirements/Operational Considerations
Descriptors: Business Case, Incident Response, Implementation Guidance, Security Policy Framework, Security Plan, Security Requirements, Standards
PCSF 2007 Meeting Feedback: Awareness at educational level, Strong alignment with safety, "How to rationally validate a security goal has been achieved?"

• Track 3 ~ Architecture/Design
Descriptors: Access Control, Application Security, Interconnections, Network
PCSF 2007 Meeting Feedback: Focused guidelines/recommended practices; Impact assessment, both pre-implementation and in-production; Requirements to consider in next generation systems; Open Source

• Track 4 ~ Devices/Components
Descriptors: Communications Security, Data Security, Field Device Security, Perimeter Devices, Remote Access
PCSF 2007 Meeting Feedback: Applying tools/techniques to device level components; Analyzing wireless practicality, utilization, and periphery applications

A solution provider categorization that is not identified by the current tracks may be accepted, but organizers reserve the right to analyze and re-adjust to present a focused program.

Preference will be given to solutions in place, presented as case studies and co-represented by an end-user. Participants in past PCSF Meetings have consistently regarded these types of interactions as the sessions that they will most likely attend.

New for the 2008 Meeting -- Solution Providers are invited to participate in an opportunity to showcase and/or demonstrate your product, services, research efforts, and share your views during our Solution Provider Night.

For additional information on criteria and guidelines for submissions, please visit: https://www.pcsforum.org/events/2008

###

More in Home