Advanced search Help
Searching for terms: EXACT: "United States. Department of Homeland Security. Office of Emergency Communications" in: publisher
Clear all search criteria
Only 2/3! You are seeing results from the Public Collection, not the complete Full Collection. Sign in to search everything (see eligibility).
-
DHS OEC FY2019 TA/SCIP Guide: Highlights & Offerings
From the Foreword: "The Office of Emergency Communications (OEC) is pleased to publish the Fiscal Year (FY) 2019 Technical Assistance (TA)/Statewide Communication Interoperability Plan (SCIP) Guide. This year's Guide includes new or enhanced offerings and approaches to help public safety and government officials meet the challenges in the rapidly changing voice and data interoperability landscape and the expanding communications ecosystem. Public safety has seen a rapid expansion in recent years in the type and manner of information sharing among responders and government officials. New applications and systems have created new challenges for interoperability. It demands good governance to drive standard operating procedures on how to use these technologies, and then joint training and exercises to ensure interoperability is achieved when needed most - at the next incident or event. In FY2019, OEC will continue delivering products and services that support interoperability in this evolving emergency communications ecosystem."
United States. Department of Homeland Security. Office of Emergency Communications
2018-10
-
National Council of Statewide Interoperability Coordinators: Strategic Plan
"The National Council of Statewide Interoperability Coordinators (NCSWIC) Strategic Plan is a stakeholder-driven, multi-jurisdictional, and multi-disciplinary strategic plan to enhance interoperable and emergency communications. The plan is a critical short-range (one year) tool to help the NCSWIC and its partners prioritize resources, strengthen governance, identify future investments, and address interoperability gaps. [...] This Strategic Plan is owned and managed by the NCSWIC. The NCSWIC Governance Committee and the NCSWIC Executive Committee (EC) have the authority to develop the Plan and are responsible for making decisions regarding the Plan. The NCSIWC EC is also responsible for ensuring that this Plan is implemented and maintained."
United States. Department of Homeland Security. Office of Emergency Communications
2018-01
-
How it Works: The Government Emergency Telecommunications Service
From the Introduction: "The Government Emergency Telecommunications Service (GETS) is an easy-to-use calling card program that provides authorized national security and emergency preparedness (NS/EP) users improved call completion on the public landline networks. It is a nationwide program providing authorized personnel priority calling during an emergency or crisis situation when the landline networks are congested and the probability of completing a call is reduced. GETS interoperates with selected government and private networks and services (FTS [Federal Technology Service] Networx; the Defense Switched Network; and the Diplomatic Telecommunications Service), and allows calls to or from international locations. The GETS card can be used with common telephone equipment, including standard desk sets, secure telephone equipment, facsimile, modems, and cellular and satellite phones."
United States. Department of Homeland Security. Office of Emergency Communications
2017-05
-
Border Interoperability Demonstration Project: Study on Rural and Urban Area Interoperability Solutions Along and Across International Borders
From the Introduction: "Interoperable communications is a fundamental challenge to all public safety agencies. Border communities face additional challenges due to technical, operational, and policy differences on both sides of the border. The 5,500 miles of U.S.-Canadian border and the nearly 2,000 miles of U.S.-Mexican border offer a diverse array of geographies, languages, and operating environments that pose unique challenges to the federal, state, local, and tribal responders operating in the regions. Furthermore, border community populations vary widely from sparsely populated rural areas and towns to more densely populated cities and metropolitan hubs. Population density impacts the types of interoperable solutions that will be most effective for a particular community. The Border Interoperability Demonstration Project (BIDP), a one-time grant administered by the Department of Homeland Security (DHS) Office of Emergency Communications (OEC), identified innovative solutions for improving interoperable communications along and across the border. One of BIDP's project objectives specifically focused on border communities of varying population densities to ensure that selected recipients included both rural and urban areas."
United States. Department of Homeland Security. Office of Emergency Communications
2017-05
-
Border Interoperability Demonstration Project: Study on Implementing Interoperability Channels Along and Across the United States-Canadian Border
From the Introduction: "Public safety agencies serving communities along the U.S.-Canadian border face unique challenges ensuring fully interoperable communications in support of their missions. For instance, agencies seeking to license radio spectrum along the border must consider regulatory policies and special restrictions that apply due to proximity to the border. These agencies must operate within terms of agreements between the Federal Communications Commission (FCC) and its international counterpart in Canada--the Innovation, Science and Economic Development Canada (ISED), formerly Industry Canada. The FCC and ISED negotiate agreements on the sharing of radio spectrum along the border in order to ensure that radio users from one country do not interfere with radio users in the other country. The agreements typically apply to any licensee operating along the border within an international coordination zone, which varies in distance from the border depending on the frequency band. Any public safety radio system constructed within an international coordination zone must also comply with technical restrictions, which are designed to prevent its radio signal from broadcasting into the other country and causing interference. Because both countries share the same radio spectrum, there are conflicts in channel assignment in certain radio bands."
United States. Department of Homeland Security. Office of Emergency Communications
2017-05
-
Border Interoperability Demonstration Project Closeout Report
From the Background: "The Department of Homeland Security (DHS) is charged with securing the international borders and strengthening preparedness and emergency response capabilities within the United States. In order to support this mission, emergency responders at all levels of government and disciplines must have the ability to communicate as needed, on demand, and as authorized, to coordinate critical security operations and to effectively respond to threats and natural disasters. Despite this mission critical requirement, many emergency responders cannot achieve interoperable emergency communications along and across the border. To address this critical need, the 'Implementing Recommendations of the 9/11 Commission Act of 2007' (Pub. L. No. 110-53) authorized the Office of Emergency Communications (OEC) to establish the Border Interoperability Demonstration Project (BIDP), a $25.5 million one-time, competitive program to provide funding and technical assistance to U.S. communities along the Canadian and Mexican borders. The legislation authorized DHS to select no fewer than six communities (at least three along the U.S.-Canadian border and at least three along the U.S.-Mexican border) for participation in the demonstration project, to provide technical assistance to the selected communities, and to share information among BIDP participants and other interested parties."
United States. Department of Homeland Security. Office of Emergency Communications
2017-04
-
Office of Emergency Communications: Fiscal Year 2017, SAFECOM Guidance on Emergency Communications Grants
"The Department of Homeland Security (DHS) is mandated to administer responsibilities and authorities relating to the SAFECOM Program. Within DHS, the Office of Emergency Communications (OEC) is responsible for developing coordinated guidance for federal grant programs for public safety interoperable communications. As a result, OEC develops the annual SAFECOM Guidance on Emergency Communications Grants (SAFECOM Guidance) as a reference guide for entities applying for federal financial assistance for emergency communications projects. While only entities funding emergency communications projects with DHS grant funding are required to comply with SAFECOM Guidance, all entities are highly encouraged to follow the recommendations within this document to ensure interoperability. The National Emergency Communications Plan (NECP) defines emergency communications as the means and methods for exchanging communications and information for successful incident management. The SAFECOM Guidance provides general information on eligible activities, technical standards, and other terms and conditions that are common to most federal emergency communications grants. The SAFECOM Guidance aims to ensure that emergency communications standards and policies across federal grant programs provide a consistent approach to improving emergency communications nationwide."
United States. Department of Homeland Security. Office of Emergency Communications
2017
-
Office of Emergency Communications Telecommunications Service Priority Operations Guide
From the Document: "This operations guide implements policy, explains legal and regulatory basis, assigns responsibilities, and prescribes procedures for the Telecommunications Service Priority (TSP) System for National Security Emergency Preparedness (NS/EP)."
United States. Department of Homeland Security. Office of Emergency Communications
2016-12
-
Facility Telecommunications Management for the Government Emergency Telecommunications Service
From the Introduction: "This document provides telecommunications management information for organizations that use the Government Emergency Telecommunications Service (GETS). It identifies information on obtaining basic facility access to GETS, and optional steps that may be taken to improve GETS access. The GETS capability is based in the public wireline telephone networks, also known as the Public Switched Telephone Network (PSTN)."
United States. Department of Homeland Security. Office of Emergency Communications
2016-12
-
Supporting and Leveraging Your Statewide Interoperability Coordinator (SWIC)
From the Document: "To do their jobs effectively, public safety responders depend on sophisticated communications systems to relay mission-critical information in real time. Today's wireless communications systems must support an ever expanding set of missions, such as responses to domestic terrorism and weapons of mass destruction, requiring coordinated participation from agencies at all levels of government. Interoperability, or the ability for emergency responders to communicate among jurisdictions, disciplines, and levels of government, using a variety of frequency bands as needed and as authorized, is crucial to responders. The Statewide Interoperability Coordinator (SWIC) assists in facilitating communications among responders during emergencies and is an important asset when responding to planned and unplanned events." This document goes on to discuss SWIC's state level role, SWIC'S state level role in supporting governance, SWIC's national level role, supporting a full-time position in your state, and concludes with frequently asked questions.
United States. Department of Homeland Security. Office of Emergency Communications
2016-05
-
Mobile Application Adoption Best Practices
This document, produced by the U.S. Department of Homeland Security Office of Emergency Communications, outlines mobile application adoption best practices. It discusses mobile application risks, how to define the benefits and seek approval regarding any given mobile application, and how to avoid security threats and maintain performance.
United States. Department of Homeland Security. Office of Emergency Communications
2016-04-13?
-
DHS Emergency Communications Forum (Volume 18)
This edition of DHS' Emergency Communications Forum contains the following articles: "A Note from OEC [Office of Emergency Communications] Leadership"; "Communications Planning for the U.S. Open"; "The Continued Importance of Emergency Communications Planning"; "2015 Maryland Command and Communications Rally"; "OEC Support for the Pope's U.S. Visit"; "OEC Supports ESF [emergency support function] #2 Activities in CNMI [Commonwealth of Northern Mariana Islands]"; "OEC Releases Emergency Communications Governance Guide"; "Southeast US EMAC [Emergency Management Assistance Compact] Deployments of COMU [All-Hazards
Communications Unit] Resources"; "Recap of Recent OEC Engagements"; "Sprint Drops WPS [ Wireless Priority Service] Subscription Fees"; and "OEC Team on the Road".
United States. Department of Homeland Security. Office of Emergency Communications
2016
-
Emergency Communications Governance Guide for State, Local, Tribal, and Territorial Officials (September 2015)
"In 2014, the Department of Homeland Security (DHS) Office of Emergency Communications
(OEC) released the National Emergency Communications Plan (NECP) with the emphasis on
enhancing decision-making, coordination, and planning for emergency communications through
strong governance structures. The 2015 Emergency Communications Governance Guide for
State, Local, Tribal, and Territorial Officials (Governance Guide) was developed to address Goal
One in the NECP, governance and leadership. The Governance Guide serves as a
comprehensive tool that provides recommendations and best practices for emergency
communications officials at all levels of government to establish, assess, and update governance
structures that represent all emergency communications capabilities (Land Mobile Radio [LMR],
broadband, 911/Next Generation 911 [NG911], alerts and warnings)."
United States. Department of Homeland Security. SAFECOM; United States. Department of Homeland Security. Office of Emergency Communications
2015-09
-
ICS-TIP-15-022-01: Best Practices for Continuity of Operations
"While infrequent in occurrence, destructive malware can present a direct threat to an organization's daily operations, impacting the availability of critical assets and data. Organizations should increase vigilance and evaluate their capabilities encompassing planning, preparation, detection, and response for such an event. This publication is focused on the threat of enterprise-scale distributed propagation methods for malware and provides recommended guidance and considerations for an organization to address as part of their network architecture, security baseline, continuous monitoring, and Incident Response practices. This paper provides recommendations and strategies that organizations can employ to actively prepare for and respond to a disruptive event such as destructive malware. These recommendations have also been posted to the US-CERT [Cyber Emergency Response Team] web site and are available at https://www.us-cert.gov/ncas/tips/ST13-003."
United States. Department of Homeland Security. Office of Emergency Communications; Industrial Control Systems Cyber Emergency Response Team
2015-01-22
-
Emergency Communications Forum - Volume 15, Spring 2015
This volume of the Department of Homeland Security Office of Emergency Communications' Emergency Communications Forum contains the following articles: "Wireless Priority Service is Crucial to Communications at Boise State Football Games"; "Coordination and Planning Lead to Successful Emergency Communications at Super Bowl XLIX [49]"; "LTE [long-term evolution] Demonstration Network at Ski Championship Gives a Glimpse into the Future of Mobile Data Use by Public Safety"; "Tabletop Exercise Allows Quapaw Tribe to Test Interoperable Communications"; "CASM [Communications Assets Survey and Mapping] Goes Mobile"; "OEC [Office of Emergency Communications] Team on the Road".
United States. Department of Homeland Security. Office of Emergency Communications
2015
-
First Responder Mobile Application Development Best Practices Guide [presentation]
From the introduction slide: "The Department of Homeland Security (DHS) developed this brochure through its Office of Emergency Communications (OEC) and the Mobile Applications for Public Safety (MAPS) program. The MAPS program is a coordination platform for the lifecycle of public safety mobile applications. Working with industry, academia and government, the MAPS program seeks to enable and streamline the development, discovery and distribution of mobile applications for first responders. In addition, MAPS promotes security, functionality and performance requirements for mobile applications for first responders."
United States. Department of Homeland Security; United States. Department of Homeland Security. Office of Emergency Communications
2014-12
-
Federal Emergency Communications Coordination
"Federal Departments and Agencies rely on emergency communications capabilities to support mission critical operations, such as law enforcement, homeland defense, and response to man-made or natural disasters. Lessons learned from the 9/11 terrorist attacks, Hurricane Katrina and Super Storm Sandy illustrate the need for improved emergency communications coordination across the Federal government and among State, Local, Tribal, and international agencies. To address these issues, Congress created the Emergency Communications Preparedness Center (ECPC), and Department of Homeland Security (DHS) Secretary Janet Napolitano established the OneDHS Emergency Communications Committee, a sub-group of the ECPC, to coordinate intra-DHS emergency communications activities. The DHS Office of Emergency Communications (OEC) administers both the ECPC and the OneDHS Emergency Communications Committee. To address interoperability issues along the U.S.- Canada border, DHS and Public Safety Canada established the Canada-United States (CANUS) Communications Interoperability Working Group (CIWG). OEC serves as co-chair of the CANUS CIWG."
United States. Department of Homeland Security. Office of Emergency Communications
2014-05
-
Technical Assistance & Statewide Communications Interoperability Plan (SCIP) Catalog [Version 4.1]
"This year's Catalog reflects the merger of the statewide planning function with legacy technical assistance into a single entity. OEC/ICTAP [Office of Emergency Services Interoperable Communications Technical Assistance Program] services are expanding and making a significant impact on our stakeholders' interoperable and emergency communications capabilities. There are several new or revised TA offerings this year including, among others, broadband workshops, new Communications Unit training courses, and a revised offerings for NG9-1-1 [Next Generation 9-1-1] and dispatch operations. New offerings are marked with a special tag by the offering name."
United States. Department of Homeland Security. Office of Emergency Communications
2014?
-
Emergency Communications Forum - Volume 12, January 2014
"The Emergency Communications Forum (ECF), published by OEC is intended to engage and inform the emergency response community, policy makers, and Federal, State, local, and tribal officials about issues and events that directly impact everyday nationwide emergency communications." This edition of the Emergency Communications Forum contains the following articles: "A Note from OEC [Office of Emergency Communications] Leadership"; "Iowa Collaboration Creates a SCIP [Statewide Communication Interoperability Plan] that Looks to the Future of Emergency Communications"; "OEC Technical Assistance Supports States in Advance of Consultations with FirstNet"; "Ohio's 'Operation Waterbug' Demonstrates BIDP [Border Interoperability Demonstration Project ]-Funded Advances"; "Supporting Emergency Communications Along the Border"; and "OEC Team on the Road".
United States. Department of Homeland Security. Office of Emergency Communications
2014-01
-
Emergency Communications Forum - Volume 13, Summer 2014
This volume of the Department of Homeland Security Office of Emergency Communications' Emergency Communications Forum contains the following articles: "With Broadband on the Horizon, the Role of the Statewide Interoperability Coordinator Is More Critical Than Ever"; "A Preview of the Updated National Emergency Communications Plan"; "CASM [Communications Assets Survey and Mapping Tool] Next Generation Tool Helps Jurisdictions Track and Deploy Communications Resources"; "OEC [Office of Emergency Communications] Releases Updated Technical Assistance Catalog to Include SCIP [Statewide Communications Interoperability Plan] Workshops"; "Oregon's Work on Broadband Is Assisting States Nationwide"; "Priority Services Unveils New GETS [Government Emergency Telecommunications Service] Card, User Resources" and "OEC Team on the Road."
United States. Department of Homeland Security. Office of Emergency Communications
2014
-
Auxiliary Communications Field Operations Guide (AUXFOG) [Version 1.0]
From the Introduction: "The Auxiliary Communications Field Operations Guide (AUXFOG) is a collection of technical reference and training information to aid trained volunteer Auxiliary Communications (AuxComm) personnel, and the agencies they serve, to supplement local emergency communications when AuxComm support is requested. AuxComm is an all-inclusive term used to describe the many organizations and personnel that provide various types of communications support to emergency management, public safety, and other government agencies. Auxiliary Communicators have been assisting the public safety community for over 100 years. These uniquely qualified communicators give their time and resources freely, without hesitation, providing auxiliary communications to NIMS/ICS [National Incident Management System Incident Command System] personnel and public safety partners. Additionally, Auxiliary Communicators frequently provide communications support during planned events, community functions, and training exercises. The contents of this guide are for training and reference, and should support the goals of your local, county, region or state government officials. It should not be used in any way to circumvent or override those established goals. Direction for the use of auxiliary communications, under NIMS/ICS, will come from either a Communications Leader (COML) or a member of the public safety agency being supported."
United States. Department of Homeland Security. Office of Emergency Communications
2013-11
-
Emergency Communications Case Study: Emergency Communications During The Response To The Boston Marathon Bombing
"The athletes competing in the 2013 Boston Marathon had prepared for months and even years to tackle the mental and physical challenges of running 26.2 miles. From the elite athletes to the middle-of-the-packers, each runner came to the starting line with a foundation of training and hard work. The same was true for the police, fire, and other emergency personnel present to support the race. It was their foundation of communications planning, training, and coordination that made a lifesaving difference when one of Boston's best days became one of its worst."
United States. Department of Homeland Security. Office of Emergency Communications
2013-08
-
Emergency Communications Case Study: Tribal Communications Partnerships - The Missing Piece In The Emergency Communications Landscape
"With 566 Federally-recognized American Indian tribes and Alaska Natives, tribal nations represent a unique and important sector of the emergency communications landscape in the United States. In an effort to assess the comprehensive nationwide interoperability for emergency communications, the DHS Office of Emergency Communications (OEC) has spent the last year coordinating with tribal nations and their neighboring counties and States to share knowledge, create plans and build partnerships that will strengthen the Nation's homeland security and emergency management system as a whole. As part of this, OEC's Interoperable Communications Technical Assistance Program (ICTAP) has been leading a data collection effort to document and gain a better understanding of the emergency communications capabilities of tribal communities across the country. The data provided by tribes has helped OEC develop technical assistance offerings focused on strengthening tribal communications and relationships between the tribe and the State. This Case Study will provide an overview of how OEC's communications assessment and workshop facilitated partnerships between the Mashpee Wampanoag tribe and its Federal, State and local public safety community to support interoperability across the Southeast Massachusetts region. One of the tribal nations that participated in OEC's data collection survey was the Mashpee Wampanoag tribe. The tribe consists of more than 2,600 enrolled members and is located primarily in Cape Cod, MA. The Wampanoags are most well-known in U.S. history for their role in the first Thanksgiving, for which they are accredited with befriending the Pilgrims of Plymouth. Hundreds of years later, the Mashpee Wampanoag tribal members still live in and around Cape Cod Bay and maintain good relations with their neighbors in Barnstable County."
United States. Department of Homeland Security. Office of Emergency Communications
2013-08
-
Emergency Communications Forum - Volume 11, July 2013
"The Emergency Communications Forum (ECF), published by OEC [Office of Emergency Communications] is intended to engage and inform the emergency response community, policy makers, and Federal, State, local, and tribal officials about issues and events that directly impact everyday nationwide emergency communications." This edition of the Emergency Communications Forum contains the following articles: "A Note from OEC Leadership"; "Using a Career's Worth of Experience to Strengthen Emergency Communications"; "Focusing on the Dispatcher's Role in Successful Emergency Communications"; "FY2013 SAFECOM Guidance on Emergency Communications Grants Released"; and "About the Office of Emergency Communications".
United States. Department of Homeland Security. Office of Emergency Communications
2013-07
-
ICS-ALERT-11-291-01B: W32.Duqu-Malware Targeting ICS Manufacturers (UPDATE)
"This updated Alert is a follow-up to the original Alert titled "ICS-ALERT-11-291-01A - W32 Duqu-malware targeting ICS Manufacturers" that was published October 20, 2011 on the ICS-CERT [Industrial Control Systems Cyber Emergency Response Team] web. [...] ICS-CERT, in close coordination with Symantec and the original researchers, has determined after additional analysis that neither industrial control systems nor vendors/manufacturers were targeted by Duqu. In addition, as of October 21, 2011, there have been very few infections and there is no evidence based on current code analysis that Duqu presents a specific threat to industrial control systems. However, organizations should still remain vigilant against this and other sophisticated malware. ICS-CERT also recommends that the ICS community update intrusion prevention systems (IPSs) and antivirus systems to detect Duqu and other new threats. ICS-CERT will continue to analyze the malware, monitor the threat landscape, and report additional information as appropriate. ICS-CERT will also continue coordination with Symantec, McAfee, the international community, and ICS Stakeholders."
United States. Department of Homeland Security. Office of Emergency Communications
2013-04-29
-
ICS-CERT Alert: ICS-ALERT-11-291-01A: W32.Duqu-Malware Targeting ICS Manufacturers (UPDATE)
"On October 18, 2011, Symantec released a Security Response Report describing W32.Duqu, an information-gathering threat targeting specific organizations, including industrial control systems (ICSs) manufacturers. According to Symantec, W32.Duqu does not contain any code related to ICSs and is primarily a remote access Trojan (RAT). Symantec reports that the original sample of W32.Duqu was gathered from a research organization based in Europe and that additional variants have been recovered from a second organization in Europe. According to Symantec, the attackers are looking for information, such as design documents, that could potentially be used in a future attack on an industrial control facility. This threat is highly targeted toward a limited number of organizations, apparently to exfiltrate data concerning their specific assets; the propagation method is not yet known. Symantec indicates that W32.Duqu is not self-replicating. Symantec reports that other attacks could be ongoing using undetected variants of W32.Duqu. Symantec states that they are continuing to analyze additional variants of W32.Duqu."
United States. Department of Homeland Security. Office of Emergency Communications
2013-04-29
-
ICS-CERT Advisory: ICSA-13-100-01: Schneider Electric MiCOM S1 Studio Improper Authorization Vulnerability
"This advisory provides mitigation details for a vulnerability affecting the Schneider Electric MiCOM S1 Studio Software. Independent researcher Michael Toecker of Digital Bond has identified an improper authorization vulnerability in the MiCOM S1 Studio Software using the Microsoft Attack Surface Analyzer tool. The vulnerability was disclosed to vendors prior to the 2013 Digital Bond S4 Conference and then presented at the conference. The function of MiCOM S1 Studio Software is to allow users to modify or manage the configuration parameters of electronic protective relays."
United States. Department of Homeland Security. Office of Emergency Communications
2013-04-10
-
ICS-CERT Advisory: ICSA-13-098-01: Canary Labs, Inc. TrendLink Insecure ActiveX Control Method
This advisory is from the Department of Homeland Security's Industrial Control Systems-Cyber Emergency Response Team (ICS-CERT), a part of the U.S. Computer Emergency Readiness Team (US-CERT). " This advisory provides mitigation details for a vulnerability in the Canary Labs, Inc. TrendLink software. Researcher Kuang-Chun Hung of Security Research and Service Institute�'Information and Communication Security Technology Center (ICST) has identified an insecure ActiveX control method vulnerability in Canary Labs, Inc. TrendLink ActiveX control. Canary Labs, Inc. has updated TrendLink, and Kuang-Chun Hung has tested the patch and verified that it mitigates the vulnerability. If exploited, an attacker could influence the paths or file names that are used in the software application. This could affect systems using TrendLink in the critical manufacturing and energy sectors in the United States, South America, and Europe. This vulnerability could be exploited remotely."
United States. Department of Homeland Security. Office of Emergency Communications
2013-04-08
-
ICS-CERT Advisory: ICSA-13-095-02: Rockwell Automation FactoryTalk and RSLinx Multiple Vulnerabilities
This advisory is from the Department of Homeland Security's Industrial Control Systems-Cyber Emergency Response Team (ICS-CERT), a part of the U.S. Computer Emergency Readiness Team (US-CERT). "Researcher Carsten Eiram of Risk Based Security has identified multiple input validation vulnerabilities in Rockwell Automation's FactoryTalk Services Platform (RNADiagnostics.dll) and RSLinx Enterprise Software (LogReceiver.exe and Logger.dll). Rockwell Automation has produced patches that mitigate these vulnerabilities, and released the patches April 5, 2013. Rockwell Automation has tested the patches to validate that they resolve the vulnerabilities. These vulnerabilities could be exploited remotely."
United States. Department of Homeland Security. Office of Emergency Communications
2013-04-05
-
ICS-CERT Advisory: ICSA-13-095-01: Cogent Real-Time Systems Multiple Vulnerabilities
This advisory is from the Department of Homeland Security's Industrial Control Systems-Cyber Emergency Response Team (ICS-CERT), a part of the U.S. Computer Emergency Readiness Team (US-CERT). "Dillon Beresford of Cimation has identified multiple vulnerabilities in the Cogent Real-Time Systems DataHub application. Cogent has produced an update that mitigates these vulnerabilities. These vulnerabilities could be exploited remotely."
United States. Department of Homeland Security. Office of Emergency Communications
2013-04-05
