Showing posts with label Freight Rail Security. Show all posts
Showing posts with label Freight Rail Security. Show all posts

Wednesday, January 30, 2013

OMB Approves Extension of TSA Rail Security ICR


Yesterday the Office of Management and Budget (OMB) approved a three year extension of the information collection request (ICR) for the rail security reporting requirements for the Transportation Security Administration (TSA). The four data collections supported by this ICR are:

Chain of Custody Documentation for transfers of railcars carrying ‘rail security-sensitive materials (RSSM) between shippers, carriers and receivers in High Threat Urban Areas (HTUA) (§1580.107);

Location and Shipping Information Reporting Burden for railcars carrying RSSM (§1580.103);

Security Concerns Reporting including security incidents, suspicious activities, and threat information (§1580.105); and

Rail Security Coordinator (RSC) Annual Reporting RSC designations and contact information (§1580.101).

These four are all required for freight railroads handling RSSM materials. The last two also apply to passenger rail systems.

ICR Changes


TSA reported that there were no changes in the proposed extension of the ICR other than an increase in the estimated number of entities reporting. As I noted in my earlier blog post about the initial 60-day public notice associated with this ICR, this is a less than accurate description of the proposed burden description. While there was an 17,603 (20%) increase in expected responses there was a decrease of 234,922 hours of burden associated with this ICR. There is no explanation in the public documentation of this ICR of where the increase in responses would come from or how there will be such a drastic (81.3%) decrease in the amount of time that the affected entities will spend on these reporting requirements. If TSA had listed the burden expectations for each of the four collections covered under this ICR we might be better able to understand these changes.

There is one other change in the ICR submission and approval that is not mentioned in the documentation for the requested ICR extension. The estimated cost burden was decreased from $9,388,567 to $0.00. I don’t think this change is due to changes in regulatory burden estimated at TSA; we have seen a total absence of estimated cost burden in all of the recent ICR renewals that I have looked at. It looks like the Obama Administration has changed their interpretation of the cost burden to only address the cost of establishing the reporting mechanism in the regulated community, not the cost of maintaining those systems and the costs associated with the actual reporting of the required information. It would be interesting to see the OMB’s justification for that change.

Information Sharing


OMB reported that they approved this ICR renewal with changes. The only change documented is an interesting requirement for TSA to look at the sharing of the collected information with the Department of Transportation (PHMSA in particular). The ICR extension approval notes that:

“Prior to resubmission, TSA should coordinate with DOT and PHMSA to explore whether there might be any opportunities to share information related to this collection. TSA should provide a joint briefing (with PHMSA) to OMB on this topic before 2/1/2014.”

It is hard to understand what freight rail safety information is covered by this ICR, but if any of this information will legitimately assist PHMSA in regulating the safe transportation of this limited segment of hazardous materials, the information should certainly be shared with PHMSA. Of course, some of this material is sensitive security information (SSI) and will have to be appropriately protected in the information sharing process.

Friday, March 2, 2012

TSA Surface Enforcement Actions 2011

Today the Transportation Security Administration (TSA) published a notice in the Federal Register (77 FR 12865) announcing the availability of their annual report for 2011 summarizing the enforcement actions undertaken by the TSA “for violations of any surface transportation requirements under title 49 of the U.S. Code (U.S.C.) and for any violations of chapter 701 of title 46 of the U.S. Code, which governs transportation worker identification credentials” (77 FR 12865).

The actual report is only three pages long but it is not printed in the Federal Register notice. To see the actual report you have to go to www.regulations.gov (Docket # TSA-2009-0024). The folks managing this web page no longer provide direct links for individual documents; the closest you can get to that is the link for the page where you can get to the document. For this year’s report that page is: http://www.regulations.gov/#!documentDetail;D=TSA-2009-0024-0008 (for the 2010 report replace the last digit with a ‘5’; and for 2009 with a ‘2’).

Summary Data


The table below shows a summary of the data for 2011.

2011 TSA Surface Enforcement Actions
# of Incidents
Maximum Penalty
Proposed
Imposed
Rail Car Chain of Custody
13
$6,000
$3,000
Rail Car Location
2
Reporting Security Concern
2
$3,000
$3,000
Use of another's TWIC
1
Allow another to use TWIC
2
$1,500
$1,500
Fraudulent Manufacture of TWIC
1
Total
21
$13,500
$8,500

Table 1: 2011 TSA Enforcement Summary

The rail car actions are based upon the freight rail security provisions at 49 CFR 1580.107. The reporting of security concerns are found in the same regulations at §1580.203. The TWIC actions are based upon §1570.7 of 49 CFR not the Coast Guard regulations regarding TWICs. The listing of these actions in the summary report also includes the case numbers for each action.

Not Much in the way of Fines


It is apparent from this report that TSA is not concerned much about collecting fines. Most of the ‘penalties’ noted in the report are administrative in nature. There are three separate administrative actions listed for the violations reported, unfortunately TSA does not provide any information about the relative level of severity or an explanation of the consequences for these actions. The three administrative actions listed are:

• Warning Notice;
• Letter of Correction; and
• Notice of Non-Compliance.

A total of only $8,500 collected in civil penalties for 21 separate enforcement actions would tend to indicate that TSA was more interested in working with the regulated community to correct security problems. That is probably a more effective use of the time available to the limited surface inspection force.

Having said that, TSA is obviously stepping up pressure to achieve compliance. In 2010 there were only 17 enforcement actions and no civil fines were levied and in 2009 (the first year of TSA’s authority to levy civil penalties) there were seven actions and not fines. Still the maximum allowed civil penalty is $10,000 and the highest fine levied was only $3,000.

While I applaud TSA’s working with industry to ensure security compliance, I was a tad bit disturbed to see no fine associated with the single instance of ‘Fraudulent Manufacture of TWIC’. That would seem to be a deliberate attempt to violate the rules which to my mind requires punishment not corrective action. Of course there are no details provided about any of these incidents, so it is really quite difficult to make an even somewhat informed second guess of the TSA’s actions in these cases.

Evolving Enforcement


The Regulation.gov web site still has the summary reports for 2009 and 2010 available for review. Table 2 below summarizes the number and types of enforcement actions completed in the first three years of the program. The one clear piece of data here is that there continues to be issues surrounding the requirements for chain of custody  documentation for rail security sensitive materials (RSSM). The limited data provided here does not allow, however, for a real assessment of how serious the problem is. To fully analyze the situation we would need to know how often, for example, TSA inspectors checked the documentation for chain of custody transfer.

2009 thru 2011 TSA Surface Enforcement Actions
# of Incidents
2009
2010
2011
Did not allow TSA Inspection
2
Rail Car Chain of Custody
2
12
13
Rail Car Security
1
Rail Car Location
2
Reporting Security Concern
1
2
Use of another’s TWIC
1
1
1
Allow another to use TWIC
1
2
Direct the use of another’s TWIC
2
Fraudulent Manufacture of TWIC
1
Use of an altered TWIC
1
Total
7
17
21

Table 2: TSA Surface Enforcement Actions thru 2011

Another area where the inspection rate data would be of particular interest is with regards to the TWIC enforcement actions. One would like to assume that TSA isn’t spending a lot of time checking general TWIC use at port facilities; that enforcement would more likely fall to the Coast Guard. It is more likely that the TSA inspectors were checking the TWICs of train crews hauling RSSM in and out of port facilities. If that’s the case, and given the small number of available TSA Surface Security Inspectors, the four TWIC enforcement actions in 2011 could indicate a serious problem with rail crews and TWICs. This could be particularly important as more high-risk, non-MTSA, chemical facilities begin to use TWICs as a method of personnel surety vetting for transportation workers.

Congressional Oversight


Congress mandated {49 U.S.C. § 114(v)(7)(A)} that TSA provide these annual reports on enforcement actions. One would assume that the purpose of the report was to allow for Congress to have a relatively easy way to monitor the progress of the surface security programs mandated by law. TSA surface security programs are a relatively small part of the TSA operations and are frequently overlooked by Congress.

In light of the problems still being uncovered at ISCD with another relatively small security program, CFATS, it might be interesting for a responsible subcommittee of either the transportation or homeland security committees (of either the House or Senate) to use the occasion of this report to conduct an oversight hearing on the implementation of the surface security inspection programs.

Friday, January 13, 2012

TSA Publishes 60-Day ICR Notice for Rail Security Program

Today the Transportation Security Administration (TSA) published in the Federal Register (77 FR 2077-2078) their 60-day notice of intent to renew their information collection request (ICR) for the rail transportation security program operated under 49 CFR 1580. The current ICR authority is scheduled to expire on April 30th, 2012.

Description of Collection Requirements


This ICR allows TSA to collect information on four separate reporting requirements in that program. Those information collections are:

Chain of Custody Documentation for transfers of railcars carrying ‘rail security-sensitive materials (RSSM) between shippers, carriers and receivers in High Threat Urban Areas (HTUA) (§1580.107);

Location and Shipping Information Reporting Burden for railcars carrying RSSM (§1580.103);

Security Concerns Reporting including security incidents, suspicious activities, and threat information (§1580.105); and

Rail Security Coordinator (RSC) Annual Reporting RSC designations and contact information (§1580.101).

NOTE: All of the CFR references listed above are only for the freight rail security program. This ICR also includes similar requirements for the last two collections for passenger rail systems.

This notice claims that the total annual burden for this ICR is 54,023 hours. This is a significant change from the original burden estimate included in the initial ICR submission back in 2008. That submission provided the following burden estimates for the four collections:

Original ICR Burden Estimates
Collection
Respondents
Responses
Burden Hours
Chain of Custody Documentation
50
18,200
219,000
Location and Shipping Information Reporting Burden
15
150
150
Security Concerns Reporting
69,483
69,483
69,483
RSC Annual Reporting Burden
945
312
312
Total

88,145
288,945

TSA should have included a more detailed description of the burden estimates in this ICR notice, especially as regards significant changes in those estimates from the current approved ICR.

Public Comments


In accordance with the Paperwork Reduction Act requirements, TSA is requesting public comments on their intent to renew this ICR. Public comments may be submitted by email to the TSA PRA Officer (TSAPRA@dhs.gov). Comments need to be submitted by March 13th to allow for an appropriate response in the required 30-day ICR notice.

Wednesday, June 15, 2011

Emerging Threats to Rail Security

Yesterday the Senate Committee on Commerce, Science, and Transportation held a full committee hearing on the emerging threats to rail security. I have not had a chance to review the video of the hearing, but a quick review of Administrator Pistole's written testimony and Chairman Rockefeller’s opening remarks continue to show that the main emphasis of the politician’s remains focused on passenger rail and transit operations, not freight rail. The GAO report that formed the written testimony of Mr. Lord does make significant observations about freight rail security matters, though it too concentrates on transit issues.

Training

The GAO report continues to take TSA to task for its failure to implement the training regulation requirements of the Implementing Recommendations of the 9/11 Commission Act of 2007. It does note that TSA reports that they intend to publish a notice of proposed rule making in the fall of this year. The report fails to note that according to the semi-annual Regulatory Agenda reports published every six months or so by DHS, TSA has had intentions of imminently publishing such an NPRM for quite some time.

Information Sharing

The GAO report addresses the multiple information sharing efforts for transit security, but notes that freight rail carriers are not satisfied with the security and intelligence information provided to them. Three of the Class I railroads that GAO interviewed for this report noted that they frequently receive intelligence information from the media before they receive the same information from TSA.

It will be interesting to see if the video of the hearing shows that the politicians on either side of the committee dais addressed these GAO concerns in their discussions during the questioning period of the hearing. I hope to have a chance to review that video this weekend.

Thursday, December 23, 2010

Fall 2010 Regulatory Agenda – Security Training

On Monday I looked at the Fall 2010 Regulatory Agenda and the pending regulations that might be of interest to the chemical security community. Yesterday I addressed the ammonium nitrate rule listed in the DHS portion of that Agenda. Today I would like to look at the TSA rule that would look at security training for freight rail employees listed in the RISC portion of the Agenda (75 FR 79563-4).

Background

Actually this is just one of the three rules listed in the Agenda where TSA will be developing security training standards but the other two deal with passenger transport modes, so they will not be of direct interest to the chemical security community. All three rules were required by different sections of the Implementing Recommendations of the 9/11 Commission Act of 2007 (PL 110-53). Section 1517 is the section that required TSA to develop these training regulations within 6 months of the enactment of that law. Since that law was passed on August 3, 2007, TSA is late, especially since they don’t currently plan to have even a notice of proposed rulemaking until March 2011.

According to the Agenda the “rulemaking will propose general requirements for a security training program to prepare freight railroad employees, including frontline employees, for potential security threats and conditions”. Any requirements will have to be justified by a cost-benefit analysis. TSA intends to look at the following potential costs:

• Creating or modifying a security training program and submitting it to TSA;
• Training (initial and recurrent) all security-sensitive employees;
• Maintaining records of employee training;
• Being available for inspections;
• Providing information on security coordinators and alternates; and
• Reporting security concerns.
DHS will then evaluate these costs against the potential benefit by using a ‘break-even analysis’ to determine the degree that the training requirements would reduce the overall risk of a terrorist attack. The risk assessment would be based upon scenarios included in the TSA Transportation Sector Security Risk Assessment.

I’m not sure how many of the scenarios might reach a break-even point for the costs of training, but I am sure that at least one scenario would clearly justify, by this type of analysis, an attack on a toxic inhalation hazard (TIH) chemical rail car in a major urban area. The number of people potentially at risk in such an attack is very large.

Delays in Rulemaking

I haven’t talked with anyone at TSA about the delays in this rulemaking, but I can make an educated guess as to at least some of the reason. First and most obvious is that surface transportation risks have always been a lower priority at TSA than air transportation. The specter of the 9/11 hijackings is the obvious reason for this as is the long history of plane hijackings. Add to that the relative ease of securing an aircraft vs a train or bus, and it is easy to see why TSA has concentrated on the low hanging fruit.

Even within the surface transportation area, freight rail is a lower priority than public transit. This too makes a certain amount of sense since it is much easier to successfully attack a passenger train than chlorine rail car. A terrorist armed with no more than a handgun or even just an acid filled squirt-gun could successfully attract world-wide attention. There would be a much higher level of technical expertise required to cause a catastrophic release of a TIH gas from a railcar.

To date TSA has limited their freight rail security regulation efforts to establishing actual standards for security of TIH rail shipments. Many will argue that the security measures are inadequate and TSA does have problems with providing acceptable measures of the actual risk reductions achieved.

Finally, TSA has included limited training requirements in their freight rail security rule. Those requirements are primarily limited to identifying improvised explosive devices. In fact TSA has produced a video that can be used in that training.

Security Training

As my readers will probably expect, I have definite ideas about what types of things should be included in any security training regulations for freight railroad employees. First and fore most, TSA has to be careful of how they define ‘security-sensitive employees’ that will be required to be trained. If they limit this training to just the ‘front-line’ employees that physically deal with trains and railcars, they will do a severe disservice to the American public. Any employee of a railroad that handles TIH chemical shipments should be considered a ‘security-sensitive’ employee for purposes of this regulation.

TSA should probably take a page from the safety training requirements used by PHMSA for hazmat shippers. The security training should follow the same two tier level of general awareness training and position specific training. Everyone should be trained on the general awareness of the terrorist threat, including:

• Explanation of current threat level,
• Discussion of potential attack consequences,
• Review of history of terror attacks on freight rail assets,
• Identification of pre-operational surveillance techniques, and
• Discussion of suspicious activity reporting procedures.
The position specific training needs to be tailored to the duties of each employee that may be required to accomplish security related task in support of the railroads efforts to prevent a successful terrorist attack on TIH railcars. The inclusion of the word ‘successful’ is very important because it needs to include emergency response measures and evacuation procedures that would be used in the event of both catastrophic and relatively ‘minor’ releases of a TIH chemical in the event of an attack (NOTE: these would mostly be the same for an accidental release).

Typically there would be a generic requirement in any rule of this sort for employees to be specifically trained on the requirement of the job outlined in the railroad security plan. Since TSA has yet to establish a requirement for railroads to have a security plan (there are only vague ‘requirements’ to conduct a vulnerability assessment), it would be difficult for TSA to include such language in a training regulation. To be fair, I suspect that most railroads do have security plans.

A key component of the job specific training would be communications measures to be used in the event of a suspected or actual attack. Not only does this need to include internal communications, but communications with local first responders. This is particularly important for train crews since they will typically transit many different jurisdictions during any train movement of any length. Being able to contact, and provide applicable information to, the local response agencies would be critical for any effective emergency-response to an attack on a TIH railcar.

Finally, any railroad employee that could reasonably be expected to be exposed to a TIH chemical release in the event of a terrorist attack (or accidental release), needs to be trained in the specific hazards associated with each TIH chemical transported by that railroad. This must include information on how the employee can identify that a release has occurred and determine how best to avoid critical exposure to the toxic cloud.

Training is a key component of any security plan. The best plan in the world will be absolutely worthless if the employees that must execute the plan are inadequately trained in its implementation. TSA has a responsibility to ensure that effective security plans are in place and that the employees are properly trained to execute those plans.

Friday, March 20, 2009

House Appropriations Looks at Rail Security Grants

A week ago Thursday, the Homeland Security Subcommittee of the House Appropriations Committee held a hearing to look at the security of transit and freight railroad operations. As befits an appropriation committee they were really looking at how efficiently TSA and FEMA were dispersing grant monies. Time Delay Note: A week ago Thursday, give me a break! What took so long? Well the Appropriations Committee Staff takes that long to get copies of prepared testimony up on their web site. This is the largest committee in the House and routinely holds five or more sub-committee hearings each day. Oh yes, and the rarely web cast their hearings. So, for those of us that live away from Washington, this is as good as it gets. Transit Systems Most of the testimony dealt with grant support for transit systems. In fact, two of the four witnesses were from major metropolitan transportation authorities. This has been the main focus of rail security since the Madrid and London bombings. It certainly makes sense. Al Qaeda and its affiliates have demonstrated their ability to attack these types of systems, so protecting US systems from similar attacks is a high priority. Freight Rail System The only witness to specifically address freight rail security was John Sammon Assistant Administrator, TSA. First he addressed the primary focus to date of the TSA freight rail program:
“The principle element of TSA’s Rail security strategy is to reduce the risk of Toxic Inhalation Hazard (TIH) chemicals in high threat urban areas. TSA works in close cooperation with the Rail industry to measure risk as a function of unattended standing TIH rail car time in high-threat urban areas. We track every TIH rail car using the Rail industry’s Automatic Car Identification readers. These readers are accurate for mainline movements, but are less accurate in complex urban areas. The Rail grant program prioritizes awards to compensate TIH tank car owners and lessors for installing Global Positioning Satellite (GPS) devices on their tank cars. The GPS devices will ensure awareness of the location of the highest risk shipments and enable appropriate security response as such shipments move into or through high consequence urban areas.”
Next he noted the priority that TSA has placed on security awareness training for frontline rail personnel in both the transit and freight side of the business. He noted that while the formal rule making process was underway to meet the 9/11 Commission Act training requirements, TSA was using grant funding to encourage and support railroad initiated programs in this area. Finally, he noted that TSA was continuing to work with railroads in conducting vulnerability assessments of high risk lines. To aid this and other enforcement actions TSA has added an additional 50 Surface Transportation Security Inspectors. Interestingly he made no mention of the recently implemented freight rail security rules (which go fully into effect on April 1st, less than two weeks from now). Freight Rail Security Low Priority From the testimony presented at this hearing it sure looks like the transit security effort remains far and away the highest priority for TSA. Very little money and effort is being expended on protecting high-risk freight rail targets from terrorist attack.

Tuesday, March 3, 2009

TSA Security Training

Even with the internet a blog writer is dependant on his readers for some information. The wider sets of connections just make more information available. For example, just yesterday I received via email copies of two TSA fliers advertising security training seminars. Since I am not on TSA mailing lists (DHS is still deciding how they really want to deal with bloggers), I never would have seen these fliers. Motor Carrier Security Training We haven’t discussed motor carrier security training too awful much in this blog. Part of that is because there just hasn’t been much in the way of regulation on hazmat security for truck shipments other than very general training (49 CFR 172.704) and security plan (49 CFR 172.800) requirements. DHS has done most of their work to date on a voluntary compliance basis, and most of that work pre-dates this blog. TSA will be conducting three-hour training sessions in eight cities this year. A total of four sessions (9am to 12pm and 1pm to 4pm on each date) are available in each city. The cities and dates are:
Tampa, FL; June 23, 24 Long Beach, CA; July 7, 8 Seattle, WA; July 21, 22 Phoenix, AZ; July 28, 29 Houston, TX; August 11, 12 Baltimore, MD; August 25, 26 Chicago, IL; September 1, 2 Newark, NJ; September 9, 10
The training will cover the training and security provisions of 49 CFR mentioned above as well as the voluntary Security Action Items (SAI) developed by TSA that can be incorporated into existing company security plans. Pre-registration can be done by email (register@tsa-sait.org) or phone (505 254-3700). For additional information contact TSA (highwaysecurity@dhs.gov). Freight Rail Security Rule Back in November of last year TSA published a new freight rail security rule. Most provisions of that rule went into effect on December 26th, but some provisions have a delayed effective date of April 1st. These rules are going to effect railroads, certain hazmat shippers and receivers. TSA is presenting a series of one-day workshops that will provide the participants with a detailed overview of the Rail Security Rule and information to assist in meeting the requirements of the regulation. There will be three presentations this month; they will be held:
March 10, 2009 – Los Angeles, California March 17, 2009 – Chicago, Illinois March 31, 2009 – Philadelphia, Pennsylvania
According to the TSA flyer the topics to be covered include:
“What’s covered in the rule “Frequently Asked Questions about the rule “Using Sensitive Security Information “Rail Security Coordinator tools of the trade “TSA Inspections: What to expect from the inspector”
The flyer does not provide any registration information, but it does provide an email address for further information; freightrailsecurity@dhs.gov.

Thursday, November 13, 2008

DHS Announces Final Rule on Railroad Security Standards

DHS announced today on its web site the publication of the TSA’s final rule on Rail Transportation Security (49 CFR parts 1520 and 1580). Official publication in the Federal Register is expected shortly. The regulations will take effect 30 days after their publication in the Federal Register. Summary of Final Rule According to the DHS Fact Sheet posted today,
“The Rail Security final rule will require freight and passenger rail carriers to designate rail security coordinators and report significant security concerns to the Transportation Security Administration (TSA). The rule also will codify TSA’s broad inspection authority. For freight rail, the rule will ensure the positive handoff of security-sensitive materials as well as establish security protocols for custody transfers of security-sensitive material rail cars between receivers of these materials that are located in high threat urban areas, shippers of these materials, and rail carriers.”
Freight Rail and PIH/TIH Chemicals According to the summary section of the final rule:
“This rule further requires that freight rail carriers and certain facilities handling specified hazardous materials be able to (1) report location and shipping information to TSA upon request and (2) implement chain of custody requirements to ensure a positive and secure exchange of specified hazardous materials. TSA also clarifies and amends the sensitive security information (SSI) protections to cover certain information associated with rail transportation.”
More Detailed Review I will be conducting a more detailed review of this final regulation in upcoming blogs.
 
/* Use this with templates/template-twocol.html */