Home  arrowright President's NSTAC   arrowright R & D Exchange 2004  arrowright Break Out Session

NSTAC Banner

Research and Development (R&D) Exchange Workshop
October 28 - October 29, 2004
Monterey, California

Break Out Session

Papers - Briefings

You will need Adobe Acrobat Reader to view .pdf files.

Breakout Papers

Human Factors Break Out Session (download the PDF version)

Background

The efficacy of any technology is directly dependent upon the ability of humans to configure, implement, and manage it as it was designed. Various factors—user awareness, organization policies and procedures, legal issues, and business pressures, among others—all shape how trust is instilled in systems. Poor user awareness or inadequate policies, for example, can manifest two problems. First, users unfamiliar with key technologies designed to engineer trust into networked information systems can inadvertently expose those systems to risk through poor configuration, implementation, or management. Second, insiders authorized to use systems they later employ for illicit purposes remain a vexing problem in terms of building trustworthy systems. Without strong protections (such as background checks, access controls, and multi-layered defenses), insiders may be able to exploit what might be technically considered a “trustworthy system.”

Recent publications focused on insider activities, including the U.S. Secret Service and CERT® Coordination Center’s Insider Threat Study: Illicit Cyber Activity in the Banking and Finance Sector, acknowledge that many reported incidents are technically unsophisticated, and thus require organizations to concentrate on their overall business processes rather than focusing narrowly on technical solutions. Additionally, as today’s virtual organizations expand to include networked associates (such as vendors, trading partners, and customers), the definition of “insider” evolves to encompass a far greater number of users necessitating increased focus on information security policies. The Insider Threat Study discusses the importance of strengthening business practices and organization policies by creating a culture of security. The study recommends that all users (from individuals responsible for data entry to system administrators to senior management) are aware of the value of security and are endowed with responsibility for responding to and reporting on suspicious behavior. In today’s environment there are limited guarantees that the integrity of software assets for national security and emergency preparedness (NS/EP) communications have not been compromised, suggesting the need for increased non-intrusive surveillance techniques to defend against malicious interference from insiders.

2003 RDX Workshop Results

At the RDX Workshop at the Georgia Tech Information Security Center at the Georgia Institute of Technology in March 2003, participants emphasized the fact that human factors pervade all aspects of trustworthiness in NS/EP telecommunications and information systems. Even the best technical solution can prove vulnerable to intentional (e.g., external attack, insider threat) or unintentional acts (e.g., defective software, inadequate system configuration, non-compliance with security policies). Participants identified seven broad areas shaping the operating environment focused on efforts to minimize the risk of inadvertent failures and malicious acts: education, training, and awareness; policy development, dissemination, and enforcement; human processing and decision-making; anomaly detection; insider threats; cultural shifts; and supply source identification.

As a result of the discussion, participants developed the following list of research priorities.

Human Factors Research Priorities

Research Area Recommended Focus
Human Processing
and Decision-Making
  • Leverage knowledge accrued from other risk management disciplines (e.g., banking, transportation, public health) to minimize biases and risks related to information security
  • Enhance tools and technologies to improve human decision-making under conditions of ambiguity or uncertainty
  • Reduce impact of human factors (e.g., number of humans interfacing with key systems) by making security transparent
Anomaly Detection
  • Research automated tools/techniques to detect anomalies (both physical access and cyber) across an entire enterprise
  • Research tools to better visualize/interpret outputs in real or near real-time from highly complex detection/anomalous activity systems (e.g., replace audit logs)
Education, Training,
and Awareness
  • Educate, train, and increase awareness of security issues (e.g., conduct market research on effective techniques to raise awareness across demographic divides)
Insider Threats
  • Investigate true prevalence of insider incidents (e.g., frequency, impact)
  • Research cultural, psychological, technical, and organizational factors that both motivate and deter insiders (e.g., what motivates an insider to act; what prevents others from exploiting known vulnerabilities)
  • Research tools and techniques to better combat insider threats
  • Translate insider threat research (existing/ongoing) into useful techniques and policies

Questions to Address

  • What progress has been made, if any, in trustworthiness R&D since March 2003 when the last RDX Workshop was held?
  • What critical challenges remain for ensuring network trustworthiness? Are these challenges the same as those raised at the last RDX Workshop? What other areas deserve consideration? Are there new challenges and issue areas not previously discussed? Are there events that have occurred since March 2003 (e.g. the Northeast blackout) that underscore additional issues to consider?
  • How can the R&D community work collaboratively to effectively share information and capitalize on collective advancements that relate to trustworthiness as communities of interest shift?
  • What roles should industry, Government, and academia (e.g., OSTP, DHS/S&T, etc.) play in advancing the trustworthiness issue? Who is responsible for leading the way and implementing past and future recommendations? Which other partners are essential or desirable to effect the recommended changes? What funding is likely necessary? From what sources?
  • Based on the session discussions, what input would you provide to OSTP in its preparation of the President’s research agenda and budget requests? What are the underlying policy issues that should be studied by the President’s NSTAC or other body?
  • What would be your three to four key points related to developing an agenda for action on trusted NS/EP telecommunications?

 

Physical Security Session (download the PDF version)

Background

Recognized as the “backbone” for all other critical infrastructures, the telecommunications sector is heavily relied upon by the United States Government, other critical infrastructures, and the general public. Consequently, threats against key telecommunications facilities could adversely affect not only the day-to-day operations of the many residential and commercial customers who rely on the networks but also the national security and emergency preparedness (NS/EP) services that run across the network. Although industry and Government have made progress in protecting the infrastructure, vulnerabilities still remain with regard to physical security at critical telecommunications facilities. Trusted systems may be compromised via damage to and/or infiltrations of the facilities in which critical telecommunications systems are housed. Significant concern arises around the structural elements of the facility as well as the trusted physical access granted to individuals requiring entrance to sites where telecommunications assets are concentrated.

The physical design of a facility may leave the key elements of the telecommunications infrastructure vulnerable to a variety of environmental and human factors. The southeastern United States is struggling to recover from an arduous hurricane season and the telecommunications infrastructure and those that rely on it are still learning critical lessons from the September 11 terrorist attacks. With the threat of both natural and man-made disasters ever looming, the telecommunications industry has sought new ways to build physical protection technologies into its networks and facilities and to identify which technologies – both new and old – provide the right combination to create a more secure environment.

In addition to the physical protections built into the structure and design of a facility, a second physical security concern relates to procedures for granting trusted access. While many facilities currently address, to some degree, the concern that unauthorized persons with malicious intent could gain access to the facility, the fear also exists that legitimate personnel with authorized access to critical facilities can have malicious intent for a variety of reasons. This type of threat is both difficult to detect and defend against. Employees, contractors, maintenance and supply workers require access to facilities housing sensitive or critical elements of the infrastructure on a regular basis. However, many facilities cannot guarantee that those granted access are trusted individuals, though they are often given unsupervised access.

Protection efforts must also consider emergency incident response situations, such as earthquake-related disaster areas and access to national special security events (NSSE), such as national political conventions and Presidential inaugurations. Communications are critical to the successful execution of both situations and telecommunications personnel will be utilized in various stages of such events. The identification of fluid methods of involvement for personnel from the telecommunications sector (and other critical infrastructures) in the continued heightened security alert state, including access to those emergency and special security events and the networks they rely on, are critical issues for industry and Government to resolve to ensure the continued trustworthiness of the network.

While industry and Government have made significant progress in their efforts to identify mitigation strategies related to both design and access related vulnerabilities, communications technologies continue to permeate the reaches of the U.S. infrastructure, pushing the issue of physical security at telecommunications facilities into new territory. Though physical security efforts have traditionally focused on the physical protection efforts related to the facilities where infrastructure components are housed, the issue has branched into the arena of logical access to critical information and networks as well. As more of the communications infrastructure becomes networked, and a greater portion of critical assets are stored in cyberspace. Consequently, those addressing the issue of physical security at telecommunications facilities are faced with the additional concern of protecting and restricting “cyber” access to their critical networks.

2003 RDX Workshop Results

At the RDX Workshop at the Georgia Tech Information Security Center at the Georgia Institute of Technology in March 2003, participants agreed on the importance of several overarching themes to characterize the state of physical security. First, they stated there were not defined or Government-validated threat scenarios or adversary attack plans against which to build measures for protecting facilities. Second, they noted the difficulty for telecommunications companies to first determine what threats existed to the industry and then protect against all feasible attack techniques. Participants also noted a lack of widespread understanding and appreciation within the industry for the sophistication of threats they face on a day-to-day basis. Finally, participants emphasized the importance of considering physical security in the context of protecting human capital, in addition to the more obvious and visible threats to physical assets. In considering R&D issues related to physical security, participants identified physical access control, information control, architectural integrity, and education and awareness as key issues in the discussion.

As a result of the discussion, participants developed the following list of research priorities they believe should be further examined through industry/Government/academic partnerships.

Physical Security Research Priorities

Research Area Recommended
Modeling and Simulation
  • Undertake advanced modeling and simulation activities for NS/EP
    events that include virtual attack/defense of facilities/networks
  • Develop a “SimFacility” simulation tool (based on SimCity-like
    capabilities) to better understand vulnerabilities and potential
    threats to physical infrastructures housing critical network components
Vulnerability Analysis
  • Develop better vulnerability analysis to understand critical single points of failure and interdependencies
Biometrics
  • Develop industry standards for and implement a biometrics based
    national standard industrial identification card
  • Utilize biometric technologies (e.g., iris scanning, hand geometry,
    facial recognition) to enhance access control processes
Critical Infrastructure Standards
  • Investigate standards for the diversity of critical infrastructures
Automated Defenses
  • Develop a system(s) for automatic defense of cable routes from
    backhoes, etc
Background Checks
  • Provide better background checks for people with access to critical
    facilities
Anomaly Detection
  • Develop a process to analyze patterns of facility use (e.g., social engineering, data mining)
Information Availability
  • Research the possibility of withdrawing critical vulnerability information from the public domain
Immune Buildings
  • Research and develop “immune” building technologies to better secure facilities against biohazard attacks

Questions to Address

  • What progress has been made, if any, in trustworthiness R&D since March 2003 when the last RDX Workshop was held?
  • What critical challenges remain for ensuring network trustworthiness? Are these challenges the same as those raised at the last RDX Workshop? What other areas deserve consideration? Are there new challenges and issue areas not previously discussed? Are there events that have occurred since March 2003 (e.g. the Northeast blackout) that underscore additional issues to consider?
  • • How can the R&D community work collaboratively to effectively share information and capitalize on collective advancements that relate to trustworthiness as communities of interest shift?
  • What roles should industry, Government, and academia (e.g., OSTP, DHS/S&T, etc.) play in advancing the trustworthiness issue? Who is responsible for leading the way and implementing past and future recommendations? Which other partners are essential or desirable to effect the recommended changes? What funding is likely necessary? From what sources?
  • Based on the session discussions, what input would you provide to OSTP in its preparation of the President’s research agenda and budget requests? What are the underlying policy issues that should be studied by the President’s NSTAC or other body?
  • What would be your three to four key points related to developing an agenda for action on trusted NS/EP telecommunications?


Cyber/Software Security Break Out Session
(download the PDF version)

Background

In its seminal report Trust in Cyberspace, the National Research Council framed a set of issues related to the trustworthiness of the Nation’s telecommunications network. Specifically, the report focused on the correctness, security, reliability, safety, and survivability of the public switched network (PSN) and the Internet; the logical elements of computer networks; and the systems, devices, and applications employed by end users. To protect against the threat of malicious software and distributed denial of service attacks, an array of technologies such as firewalls, intrusion detection systems, and virtual private networks have been researched, developed, and fielded. The effectiveness of those technologies, however, is limited by several factors, including the inability to keep pace with attack profiles, interoperability issues between proprietary solutions, inconsistent patch implementation, and the increasing complexity of the telecommunications network as a result of convergence activities.

Network trustworthiness may be defined as the expectation that systems on that network will do what they are supposed to do and not do what they are not supposed to do. As such, software plays an integral role in achieving trustworthiness, as it is the software that integrates and customizes general-purpose system components to accomplish any given task. Consequently, inadequate software security can have many far-reaching negative consequences that detract from the overall trustworthiness of information systems. Factors related to software that can affect the trustworthiness of systems include, but are not limited to: (1) complex source code that could contain millions of lines of code to be tested and evaluated in short time periods; (2) the connection of legacy systems to more current, diverse systems; (3) the movement toward using commercial off the shelf software, which in many cases causes developers to become dependent on third party vendors for the design and security of important components; (4) the inability to ensure that system administrators are updating system software patches in a timely manner; and (5) other influences, such as standards and/or regulations that compete with efforts to develop trusted systems.

These security issues have considerable impact for national security and emergency preparedness (NS/EP) stakeholders and the technologies upon which they rely. Additionally, of increasing concern to the NS/EP community during recent years is the growing prevalence of spyware, which represents a significant challenge for industry and Government because of a number of associated security implications: loss of sensitive and/or proprietary information, loss of privacy, loss of bandwidth, loss of system integrity, and loss of resources.

Many advances have been made in the arena of cyber and software security, including the creation of the National Cyber Security Division within the Department of Homeland Security’s Information Analysis and Infrastructure Protection Directorate to address the concerns related to the Nation’s cyber security posture and the National Security Agency’s recent proposal to create a government-funded research center devoted to improving the security of commercial software. However, new technological advancements and the increasing global access to the Internet only serve to increase the difficulty of ensuring network trustworthiness. As the nature of the network continues to change, so too will the discussions related to trustworthiness.

2003 RDX Workshop Results

At the RDX Workshop at the Georgia Tech Information Security Center at the Georgia Institute of Technology in March 2003, participants determined that protecting NS/EP mission-critical systems and ensuring their reliability had become a responsibility not only of the U.S. Government but also that of the private sector, the primary owner and operator of critical infrastructure. Participants emphasized the Nation needed to expect and, in turn, develop strategies to eliminate more sophisticated threats likely to be unleashed in the future. They noted today’s security practitioners were responding to hackers defacing websites or stealing credit card numbers. In the future, however, highly organized terrorist organizations (and possibly hostile foreign countries) might launch more sophisticated, widespread, and debilitating attacks, exploiting vulnerabilities in the information infrastructure.

Several participants noted how R&D investments in cyber security were minimal in the 1980s, and how the results of that neglect were visible today. They stated the increasing reliance on commercial off-the-shelf products had reduced overall cost, but also caused users to become dependent on third party vendors for the design and security of important components. Others stated the U.S. Government, reluctant to regulate the Internet to avoid stifling competition, had mainly delegated the responsibility to protect the Nation’s critical telecommunications infrastructure to the private sector. They noted, however, that market objectives and national security concerns were not always harmonious. They stated the primary motivation for a company was to increase profitability and market presence. Therefore, most participants agreed that reliance on pure market forces was unlikely to produce a business case conducive to spending valuable resources on security protections. The group also expressed an overall sense of frustration at the political and bureaucratic processes driving research in cyber security technologies, noting many of today’s security vulnerabilities were identified more than a decade ago, but little progress had been made in eliminating them.

As a result of the discussion, participants recommended that the Office of Science and Technology Policy focus on R&D activities in two dimensions: (1) short-term research that could improve the trustworthiness of software and cyber systems in the near future and (2) long-term research that could embed the concept of trustworthy computing in the design of future systems. These priorities are summarized below:


Cyber Security and Software Priorities

Research Area Recommended
Economic Incentives
  • Develop and encourage the creation of market incentives designed to stimulate research in security technologies. Those incentives could include, but not be limited to, tax breaks and credits, subsidies, or any other monetary incentives
Vulnerabilities
  • Develop methods and tools to eliminate vulnerabilities in software during the design and development phases, particularly with source code
  • Develop techniques to automatically test for vulnerabilities in COTS
  • Develop validation and quality assurance techniques to ensure that appropriate software patches are installed
  • Develop and deploy computer security embedded measures (e.g. trustworthy code, secure default mechanisms)†
    Design compilers to scan source code and identify, if not remove, vulnerabilities†
Secure Protocol Design and
Development
  • Promote secure protocol design by analyzing current routing and signaling protocols (e.g. BGP) and incorporating findings into the design of future protocols
Legacy System Security
  • Implement techniques to strengthen the security of legacy systems
Priority Routing
  • Develop a GETS-like program for priority packet routing in all networks with assured quality of service for use during emergency situations
Modeling and Simulation Mechanisms
  • Develop modeling, simulation, and analytic techniques and mechanisms to pinpoint systemic weaknesses and better prepare for and respond to emergencies
  • Model and simulate networks to map network topologies and monitor Internet traffic
  • Develop early warning systems to prevent and respond to cyber attacks†
System-wide Recovery and Remediation
  • Improve system-wide recovery and remediation to create more robust network systems that respond more quickly to attacks
Intelligent Agents
  • Research methods, such as intelligent agents, to monitor traffic electronically, configure systems, and enforce security policies automatically
Information Sharing
  • Determine what information should be shared amongst infrastructure owners
  • Create data collection system to help generate a business model for sharing
Risk Assessments
  • Promote the development of risk assessment methodologies to help analyze the costs associated with implementing/not implementing security mechanisms
Best Practices
  • Conduct impact analyses to assess the efficacy of best practices and evaluate how they are implemented
Cyber Security Research
  • Support basic research in the science of cyber security to include building and deploying inherently secure architectures; testing and evaluating large-scale systems; defining rules of composition for large-scale systems; and defining and developing technical metrics that measure the strength of security†
  • Design compilers that eliminate or (at least) identify vulnerabilities during compilation of software applications
Embedded Systems
  • Promote the security of “embedded systems” where old architectures have been integrated into new, more security oriented architectures†
Advanced Investigative
Tool Development
  • Develop tools for authentication, forensics, and attribution to facilitate international investigations and foster cooperation†
System Criticality
  • Determine the criticality of specific systems to better understand the potential impact of specific system vulnerabilities and to rationalize and prioritize investments to protect, mitigate, and eliminate those with the greatest potential economic/performance impact
Security Metrics
  • Develop and verify security metrics for use on a national level to create a much-improved environment and common format for sharing intrusion information
Information Assurance Decision Making
  • Develop decision support tools to help organizations better understand how security products and applications might impact system performance and assess economic impacts (e.g., return on investment)
Internet System Dynamics
  • Develop a clearer understanding of the Internet’s system dynamics including reconciling the security roles, responsibilities, and relationships between the “end-nodes” and the intermediaries
  • Create a national cyber command and control system to develop and implement a national process for cyberspace indications and warning and develop national benchmarks for trustworthiness of NS/EP telecommunications systems based on different levels of criticality that would improve the health of the Internet
Well-Trained Workforce
  • Promote the development of a more well-trained workforce for research, development, and operation
  • Increase emphasis on security, trustworthiness, and cyber ethics at academic and training institutions
Trustworthiness
  • Improve the “building blocks” of trustworthiness – better attribution and damage prevention/limitation
Policy Development
  • Develop policy fostering cooperation, collaboration, and prosecution for the mutual protection of national and international infrastructures
† - Denotes Long-Term Focus


Questions to Address

  • What progress has been made, if any, in trustworthiness R&D since March 2003 when the last RDX Workshop was held?
  • What critical challenges remain for ensuring network trustworthiness? Are these challenges the same as those raised at the last RDX Workshop? What other areas deserve consideration? Are there new challenges and issue areas not previously discussed? Are there events that have occurred since March 2003 (e.g. the Northeast blackout) that underscore additional issues to consider?
  • How can the R&D community work collaboratively to effectively share information and capitalize on collective advancements that relate to trustworthiness as communities of interest shift?
  • What roles should industry, Government, and academia (e.g., OSTP, DHS/S&T, etc.) play in advancing the trustworthiness issue? Who is responsible for leading the way and implementing past and future recommendations? Which other partners are essential or desirable to effect the recommended changes? What funding is likely necessary? From what sources?
  • Based on the session discussions, what input would you provide to OSTP in its preparation of the President’s research agenda and budget requests? What are the underlying policy issues that should be studied by the President’s NSTAC or other body?
  • What would be your three to four key points related to developing an agenda for action on trusted NS/EP telecommunications?

Briefings


Questions or comments concerning this site? Please contact the webmaster.

Reviewed December 07, 2006

Privacy Policy

NCS Web Banner Department of Homeland Security