tag:blogger.com,1999:blog-15553764509703529632024-03-12T16:28:25.009-07:00Maritime Security/MTSA NewsThis blog will post the latest news on regulations and policy affecting facilities subject to 33 CFR 105 and vessels subject to 33 CFR 104.Laurie Thomashttp://www.blogger.com/profile/16611719448125721800noreply@blogger.comBlogger137125tag:blogger.com,1999:blog-1555376450970352963.post-34861814563393375472020-03-04T12:02:00.000-08:002020-03-04T12:02:42.870-08:00Suggestions for Facility Security Officers (FSOs) Concerning COVID-19 (Corona Virus) Response<br />
<div class="MsoNormal">
Below are some suggestions for Facility Security Officers (FSOs)
who are thinking about COVID-19 (corona virus) response. These suggestions are
generated from conversations with other FSOs, with health care professionals, and
from the cited references. <o:p></o:p></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
1. Let’s pay attention to what every single solitary health
professional is telling us and wash our hands.<span style="mso-tab-count: 1;"> </span>
Make it both mandatory and easy for employees to wash their hands. Restaurants
have signs stating, “Employees must wash their hands before leaving restroom.”
Consider instituting this policy; it is one way to ensure periodic
hand-washing. Make sure that the soap dispensers in the restroom and breakroom are
full. Make this someone’s responsibility and put it in writing. <o:p></o:p></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
Make alcohol-based hand sanitizer (at least 60 – 95%
alcohol) available when it is not possible to use soap and water. Portable hand
sanitizer stands are available online but these stands are something that the
facility can craft itself.<o:p></o:p></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
2. Make expectations for workplace behavior clear. Don’t
assume that employees know that they should wash their hands, perform good
cough and sneeze etiquette, stay home when sick, etc. Posters concerning these
issues can be found on the Centers for Disease Control website at <a href="https://www.cdc.gov/nonpharmaceutical-interventions/tools-resources/educational-materials.html">https://www.cdc.gov/nonpharmaceutical-interventions/tools-resources/educational-materials.html</a>
. It’s really important for employers to make their expectations about
workplace behavior very clear and these posters are a good way to do it.<o:p></o:p></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
3. Perform routine environmental cleaning. From the CDC: “Routinely
clean all frequently touched surfaces in the workplace, such as workstations,
countertops, and doorknobs. Use the cleaning agents that are usually used in
these areas and follow the directions on the label. No additional disinfection
beyond routine cleaning is recommended at this time. Provide disposable wipes
so that commonly used surfaces (for example, doorknobs, keyboards, remote
controls, desks) can be wiped down by employees before each use.”<o:p></o:p></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
4. Distance is your friend. The health professionals are
telling us to stay 6’ from other persons when possible. For example: if you are
having a meeting, move the chairs further apart. If you are walking around the
terminal, space yourselves out.<o:p></o:p></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
5. If you get into a situation where you must be around persons
whose health status is not known to you (like aboard the vessel), you should take
all reasonable precautions. If possible wear latex gloves.<span style="mso-spacerun: yes;"> </span>Maintain a good space from the crew. Minimize
touching handrails, etc. with your bare hands. A reasonable precaution may be
to have one person along just to watch for and report on possible contamination.
This person’s duties and responsibilities will only consist of this monitoring.
Politely decline beverages and food. Although currently there is no evidence to
support transmission of COVID-19 associated with food, <span style="mso-spacerun: yes;"> </span>situations that might involve transmission of
respiratory droplets should be avoided. <span style="mso-spacerun: yes;"> </span>Use
hand sanitizer as soon as possible and thoroughly wash hands (for 20 seconds)
as soon as possible.<o:p></o:p></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
6. Be familiar with the latest policy on COVID-19. Coast
Guard Maritime Commons blog (<a href="https://mariners.coastguard.blog/">https://mariners.coastguard.blog/</a>)
informs the maritime community when these documents are issued. <o:p></o:p></div>
<div class="MsoNormal">
</div>
<ul>
<li>The Coast Guard has issued Marine Safety Information
Bulletin 01-20 Novel Coronavirus Precautions at <a href="https://www.dco.uscg.mil/Portals/9/DCO%20Documents/5p/MSIB/2020/MSIB-01-20-Novel-Coronavirus-Precautions-USCG.pdf?ver=2020-01-24-192641-323">https://www.dco.uscg.mil/Portals/9/DCO%20Documents/5p/MSIB/2020/MSIB-01-20-Novel-Coronavirus-Precautions-USCG.pdf?ver=2020-01-24-192641-323</a>.
The MSIB states that “Local industry stakeholders, in partnership with their
Coast Guard Captain of the Port, should review and be familiar with section
5310 Procedures for Vessel Quarantine and Isolation, and Section 5320 -
Procedures for Security Segregation of Vessels in their Area Maritime Security
Plan (AMSP).” These plan sections detail the steps that the Captain of the Port
will take to ensure that the vessel is quarantined or a security segregation is
accomplished. (It has been my experience that many FSOs are not familiar with the
details of their AMSP and do not have a copy. Many FSOs do not attend AMSC
meetings.)</li>
<li>The Maritime Administration (MARAD) has issued Maritime
Security Communications with Industry (MSCI) Advisory 2020-004-Global-Novel
Coronavirus Outbreak., at <a href="https://www.maritime.dot.gov/content/2020-004-global-novel-coronavirus-outbreak">https://www.maritime.dot.gov/content/2020-004-global-novel-coronavirus-outbreak</a>.
This communication states, “Illness of a person onboard a vessel that may
adversely affect the safety of a vessel or port facility is a hazardous
condition per 33 CFR 160.216 and must be reported to the U.S. Coast Guard COTP
under 33 CFR 160.206. Suspected cases of 2019-nCoV must be reported to the
COTP.”</li>
<li>The CDC’s main site for information on COVID-19 is <a href="https://www.cdc.gov/coronavirus/2019-ncov/index.html">https://www.cdc.gov/coronavirus/2019-ncov/index.html</a></li>
<li>A good guide for COVID-19 and employers, Interim Guidance
for Businesses and Employers to Plan and Respond to Coronavirus Disease 2019
(COVID-19), February 2020, is found at https://www.cdc.gov/coronavirus/2019-ncov/specific-groups/guidance-business-response.html</li>
<li>The Centers for Disease Control (CDC) has a page concerning
COVID-19 recommendations for ships, at <a href="https://www.cdc.gov/quarantine/maritime/recommendations-for-ships.html">https://www.cdc.gov/quarantine/maritime/recommendations-for-ships.html</a>,
Interim Guidance for Ships on Managing Suspected Coronavirus Disease 2019.</li>
<li>42 CFR 71.21 requires ships’ masters to report to the CDC or
to nearest the port at which the ship will arrive, the occurrence, on board, of
any death or any ill person among passengers or crew (including those who have
disembarked or have been removed) during the 15-day period preceding the date
of expected arrival or during the period since departure from a U.S. port
(whichever period of time is shorter).</li>
</ul>
<o:p></o:p><br />
<div class="MsoNormal">
<o:p></o:p></div>
<div class="MsoNormal">
<o:p></o:p></div>
<div class="MsoNormal">
<o:p></o:p></div>
<div class="MsoNormal">
<o:p></o:p></div>
<div class="MsoNormal">
<o:p></o:p></div>
<div class="MsoNormal">
7. Find out what practical steps you should take if you discover
that multiple persons on the vessel are sick and guess what! no one has
reported it to anybody. CBP, the ships chandlers, the dock crew, have all been
aboard. Talk to your local health department; they may have an outbreak plan. <b><i>Do
not assume that they know anything about your operations or the vessels that
come into your dock.<o:p></o:p></i></b></div>
<div class="MsoNormal">
Granted, vessel representatives are required to report sick
or deceased crew/passengers within the last 15 days to the CDC under 42 CFR
71.21. However - <span style="mso-spacerun: yes;"> </span>I am concerned that the
flow of information CDC > U.S. Coast Guard > individual facility might somehow
stovepipe. Here is what is supposed to happen, from the MARAD advisory “The
Coast Guard will continue to review all “Notice of Arrivals” in accordance with
current policies and will communicate any concerns stemming from sick or
deceased crew or passengers to their Coast Guard chain of command and the CDC
quarantine station who will coordinate with local health authorities.” <o:p></o:p></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
8.<span style="mso-spacerun: yes;"> </span>Keep the Coast
Guard informed at once of any situation that might involve the maritime nexus
and COVID-19.<o:p></o:p></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
Just my opinion: I don't think we can make the distinction
that COVID-19 is a safety, not a security issue. Security activities such as
screening may bring employees into contact with other people in a manner that
was acceptable six months ago but may not be acceptable today, so this virus is
very much a security manager's concern.<o:p></o:p></div>
<br />Laurie Thomashttp://www.blogger.com/profile/16611719448125721800noreply@blogger.com0tag:blogger.com,1999:blog-1555376450970352963.post-73353552702379572962019-04-08T13:57:00.000-07:002019-04-08T13:57:51.314-07:00Coast Guard Office of Port and Facility Compliance Issues 2018 Year in Review<div class="separator" style="clear: both; text-align: center;">
</div>
<br />
<div class="MsoNormal">
On May 05, 2019, Coast Guard Maritime Commons, the Coast
Guard’s blog for maritime professionals, published a notice that the Office of
Port and Facility Compliance (CG-FAC) has issued its Annual Review, available
on the CG-FAC website. The Maritime Commons post is at <a href="https://mariners.coastguard.dodlive.mil/2019/04/05/4-5-2019-port-and-facility-compliance-annual-report-published/">https://mariners.coastguard.dodlive.mil/2019/04/05/4-5-2019-port-and-facility-compliance-annual-report-published/</a><span style="mso-spacerun: yes;"> </span>The Year in Review report is at the bottom of
the CG-FAC homepage at https://www.dco.uscg.mil/Our-Organization/Assistant-Commandant-for-Prevention-Policy-CG-5P/Inspections-Compliance-CG-5PC-/cgfac/<o:p></o:p></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
As stated in the document, “The mission of the Office of
Port and Facility Compliance (CG-FAC) is to provide safety, security, and
environmental stewardship for the nation’s ports and facilities.”<a href="file:///C:/Users/lthom_000/Desktop/CG-FAC%202018%20Year%20in%20Review.docx#_edn1" name="_ednref1" style="mso-endnote-id: edn1;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "Calibri",sans-serif; font-size: 11.0pt; line-height: 107%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;">[1]</span></span><!--[endif]--></span></span></a>
Cargo and container security, facility security, TWIC, cyber security, the Area
Maritime Security Committees, and most of the Maritime Transportation Security
Act of 2002 (MTSA) activities vital to Facility Security Officers are managed from
this office. This is a short, very readable document. The very important
activities of this Office in 2018 are presented in brief summaries. There are
often links included to source documents.<o:p></o:p></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
Topics addressed in the report include:<o:p></o:p></div>
<ul>
<li><span style="font-family: Symbol; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol;"><span style="mso-list: Ignore;">·<span style="font: 7.0pt "Times New Roman";"> </span></span></span>Highlights of 2018:</li>
<li><span style="font-family: "Courier New"; text-indent: -0.25in;">o<span style="font-family: "Times New Roman"; font-size: 7pt; font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal;">
</span></span><span style="text-indent: -0.25in;">Marine Transportation System Recovery</span></li>
<li><span style="font-family: "Courier New"; mso-fareast-font-family: "Courier New";"><span style="mso-list: Ignore;">o<span style="font: 7.0pt "Times New Roman";">
</span></span></span><!--[endif]-->Biennial Facility Inspector & Port Security
Specialist Workshop </li>
<li><span style="font-family: "Courier New"; mso-fareast-font-family: "Courier New";"><span style="mso-list: Ignore;">o<span style="font: 7.0pt "Times New Roman";">
</span></span></span><!--[endif]-->Committee for the Marine Transportation System
(CMTS) Workshop </li>
<li><span style="font-family: "Courier New"; mso-fareast-font-family: "Courier New";"><span style="mso-list: Ignore;">o<span style="font: 7.0pt "Times New Roman";">
</span></span></span><!--[endif]-->Common Assessment and Reporting Tool (CART) </li>
<li><span style="font-family: "Courier New"; mso-fareast-font-family: "Courier New";"><span style="mso-list: Ignore;">o<span style="font: 7.0pt "Times New Roman";">
</span></span></span><!--[endif]-->Explosive Handling Supervisor Program Manual </li>
<li><span style="font-family: "Courier New"; mso-fareast-font-family: "Courier New";"><span style="mso-list: Ignore;">o<span style="font: 7.0pt "Times New Roman";">
</span></span></span><!--[endif]-->Regulated Bulk Liquid Transfer Monitor Manual </li>
<li><span style="font-family: "Courier New"; mso-fareast-font-family: "Courier New";"><span style="mso-list: Ignore;">o<span style="font: 7.0pt "Times New Roman";">
</span></span></span><!--[endif]-->API 570 Policy Letters </li>
<li><span style="font-family: "Courier New"; mso-fareast-font-family: "Courier New";"><span style="mso-list: Ignore;">o<span style="font: 7.0pt "Times New Roman";">
</span></span></span><!--[endif]-->International Engagement </li>
<li><span style="font-family: "Courier New"; mso-fareast-font-family: "Courier New";"><span style="mso-list: Ignore;">o<span style="font: 7.0pt "Times New Roman";">
</span></span></span><!--[endif]-->Arctic Work on Prevention of Pollution of the
Marine Environment </li>
<li><span style="font-family: "Courier New"; mso-fareast-font-family: "Courier New";"><span style="mso-list: Ignore;">o<span style="font: 7.0pt "Times New Roman";">
</span></span></span><!--[endif]-->Liquefied Natural Gas (LNG) Facility Support </li>
<li><span style="font-family: "Courier New"; mso-fareast-font-family: "Courier New";"><span style="mso-list: Ignore;">o<span style="font: 7.0pt "Times New Roman";">
</span></span></span><!--[endif]-->Reporting of Inadequate Port Reception
Facilities </li>
<li><span style="font-family: "Courier New"; mso-fareast-font-family: "Courier New";"><span style="mso-list: Ignore;">o<span style="font: 7.0pt "Times New Roman";">
</span></span></span><!--[endif]-->Marine Information for Safety & Law
Enforcement (MISLE) Enhancements </li>
<li><span style="font-family: "Courier New"; mso-fareast-font-family: "Courier New";"><span style="mso-list: Ignore;">o<span style="font: 7.0pt "Times New Roman";"> </span></span></span><!--[endif]-->Policy
Advisory Council (PAC) Document Registry </li>
<li><span style="font-family: "Courier New"; mso-fareast-font-family: "Courier New";"><span style="mso-list: Ignore;">o<span style="font: 7.0pt "Times New Roman";">
</span></span></span><!--[endif]-->National Maritime Security Advisory Committee
(NMSAC) </li>
<li><span style="font-family: Symbol; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol;"><span style="mso-list: Ignore;">·<span style="font: 7.0pt "Times New Roman";">
</span></span></span><!--[endif]-->Cyber Risk Management </li>
<li><span style="font-family: Symbol; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol;"><span style="mso-list: Ignore;">·<span style="font: 7.0pt "Times New Roman";">
</span></span></span><!--[endif]-->Unmanned Aerial Systems (UAS) </li>
<li><span style="font-family: Symbol; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol;"><span style="mso-list: Ignore;">·<span style="font: 7.0pt "Times New Roman";">
</span></span></span><!--[endif]-->2018 Statistics </li>
<li><span style="font-family: Symbol; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol;"><span style="mso-list: Ignore;">·<span style="font: 7.0pt "Times New Roman";">
</span></span></span><!--[endif]-->Container Updates </li>
<li><span style="font-family: Symbol; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol;"><span style="mso-list: Ignore;">·<span style="font: 7.0pt "Times New Roman";">
</span></span></span><!--[endif]-->Rulemakings </li>
<li><span style="font-family: Symbol; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol;"><span style="mso-list: Ignore;">·<span style="font: 7.0pt "Times New Roman";">
</span></span></span><!--[endif]-->Training </li>
<li><span style="font-family: Symbol; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol;"><span style="mso-list: Ignore;">·<span style="font: 7.0pt "Times New Roman";">
</span></span></span><!--[endif]-->Area Maritime Security Committees </li>
<li><span style="font-family: Symbol; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol;"><span style="mso-list: Ignore;">·<span style="font: 7.0pt "Times New Roman";">
</span></span></span><!--[endif]-->On the Horizon for 2019<span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><a href="file:///C:/Users/lthom_000/Desktop/CG-FAC%202018%20Year%20in%20Review.docx#_edn2" style="mso-endnote-id: edn2;" title=""><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "Calibri",sans-serif; font-size: 11.0pt; line-height: 107%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;">[2]</span></span></a></span></span> </li>
</ul>
<!--[if !supportLists]--><o:p></o:p><br />
<div class="MsoListParagraphCxSpMiddle" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 1.0in; margin-right: 0in; margin-top: 0in; mso-add-space: auto; mso-list: l0 level2 lfo1; text-indent: -.25in;">
<o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 1.0in; margin-right: 0in; margin-top: 0in; mso-add-space: auto; mso-list: l0 level2 lfo1; text-indent: -.25in;">
<o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 1.0in; margin-right: 0in; margin-top: 0in; mso-add-space: auto; mso-list: l0 level2 lfo1; text-indent: -.25in;">
<o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 1.0in; margin-right: 0in; margin-top: 0in; mso-add-space: auto; mso-list: l0 level2 lfo1; text-indent: -.25in;">
<o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 1.0in; margin-right: 0in; margin-top: 0in; mso-add-space: auto; mso-list: l0 level2 lfo1; text-indent: -.25in;">
<o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 1.0in; margin-right: 0in; margin-top: 0in; mso-add-space: auto; mso-list: l0 level2 lfo1; text-indent: -.25in;">
<o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 1.0in; margin-right: 0in; margin-top: 0in; mso-add-space: auto; mso-list: l0 level2 lfo1; text-indent: -.25in;">
<o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 1.0in; margin-right: 0in; margin-top: 0in; mso-add-space: auto; mso-list: l0 level2 lfo1; text-indent: -.25in;">
<o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 1.0in; margin-right: 0in; margin-top: 0in; mso-add-space: auto; mso-list: l0 level2 lfo1; text-indent: -.25in;">
<o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 1.0in; margin-right: 0in; margin-top: 0in; mso-add-space: auto; mso-list: l0 level2 lfo1; text-indent: -.25in;">
<o:p></o:p></div>
<span style="mso-bookmark: _Hlk5629384;"></span>
<div class="MsoListParagraphCxSpMiddle" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 1.0in; margin-right: 0in; margin-top: 0in; mso-add-space: auto; mso-list: l0 level2 lfo1; text-indent: -.25in;">
<o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-add-space: auto; mso-list: l0 level1 lfo1; text-indent: -.25in;">
<o:p></o:p></div>
<span style="mso-bookmark: _Hlk5627810;"></span>
<div class="MsoListParagraphCxSpMiddle" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-add-space: auto; mso-list: l0 level1 lfo1; text-indent: -.25in;">
<o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-add-space: auto; mso-list: l0 level1 lfo1; text-indent: -.25in;">
<o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-add-space: auto; mso-list: l0 level1 lfo1; text-indent: -.25in;">
<o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-add-space: auto; mso-list: l0 level1 lfo1; text-indent: -.25in;">
<o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-add-space: auto; mso-list: l0 level1 lfo1; text-indent: -.25in;">
<o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-add-space: auto; mso-list: l0 level1 lfo1; text-indent: -.25in;">
<o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="line-height: normal; margin-bottom: .0001pt; margin: 0in; mso-add-space: auto;">
While all of these topics are important,
here are several that really caught my attention. <o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="line-height: normal; margin-bottom: .0001pt; margin: 0in; mso-add-space: auto;">
<br /></div>
<div class="MsoListParagraphCxSpMiddle" style="line-height: normal; margin-bottom: .0001pt; margin: 0in; mso-add-space: auto;">
First of all, <b style="mso-bidi-font-weight: normal;">2018 enforcement statistics:<o:p></o:p></b></div>
<br />
<div class="MsoListParagraphCxSpMiddle" style="line-height: normal; margin-bottom: .0001pt; margin: 0in; mso-add-space: auto;">
From 2018 Year in Review<o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="line-height: normal; margin-bottom: .0001pt; margin: 0in; mso-add-space: auto;">
<br /></div>
<div class="MsoListParagraphCxSpMiddle" style="line-height: normal; margin-bottom: .0001pt; margin: 0in; mso-add-space: auto;">
It’s no surprise that access control
generates the most citations of the top five. Next in line comes owner/operator
requirements, followed by drill and exercise requirements, then comes a tie
between restricted area and reporting (breach of security). Facility inspectors
across multiple Coast Guard Sectors have been stating that reporting is
becoming an area of concern. This is confirmed here. Four out of the top 5 citations
appeared in LCDR Jennifer Osburn’s excellent 2017, report, MTSA Effectiveness<a href="file:///C:/Users/lthom_000/Desktop/CG-FAC%202018%20Year%20in%20Review.docx#_edn3" name="_ednref3" style="mso-endnote-id: edn3;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "Calibri",sans-serif; font-size: 11.0pt; line-height: 107%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;">[3]</span></span><!--[endif]--></span></span></a>,
which listed these violations, 1) Access Control, 2) Restricted Areas, 3)
Drills & Exercises, 4)Owner/Operator Requirements, and 5) Audits &
VSP/ASP Amendments (stating that they were not in order and were “common” and “typical”).<o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="line-height: normal; margin-bottom: .0001pt; margin: 0in; mso-add-space: auto;">
<br /></div>
<div class="MsoListParagraphCxSpMiddle" style="line-height: normal; margin-bottom: .0001pt; margin: 0in; mso-add-space: auto;">
<b style="mso-bidi-font-weight: normal;">Cyber
risk management:</b> <o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-add-space: auto;">
While the draft Cyber NVIC is
going through review, units are encouraged to engage in conversations with
facility owners, operators, and security officers about facilities’
cybersecurity/cyber risk management programs and how to begin incorporating
cyber into FSAs and FSPs. The Cyber NVIC itself is an awareness tool to inform
industry of the requirement to include cyber and provides examples of how cyber
might relate to cites within 33 CFR 105 and 106. The NVIC itself is not a
template for a Facility Security Plan (FSP) update, addendum, or otherwise example,
and therefore addressing cyber risks should not pend on its publication.<a href="file:///C:/Users/lthom_000/Desktop/CG-FAC%202018%20Year%20in%20Review.docx#_edn4" name="_ednref4" style="mso-endnote-id: edn4;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "Calibri",sans-serif; font-size: 11.0pt; line-height: 107%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;">[4]</span></span><!--[endif]--></span></span></a><o:p></o:p></div>
<div class="MsoListParagraphCxSpMiddle" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-add-space: auto;">
<br /></div>
<div class="MsoListParagraphCxSpLast" style="line-height: normal; margin-bottom: .0001pt; margin: 0in; mso-add-space: auto;">
<b style="mso-bidi-font-weight: normal;">Unmanned
Aerial Systems (UAS) <o:p></o:p></b></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
There is an excellent discussion here of a best practice from Sector
New Orleans, focusing on focus on tracking authorized UAS flights rather than
trying to determine unauthorized flights.<o:p></o:p></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in;">
In an effort to
support this established novel practice, CG-FAC is working with the Coast Guard<o:p></o:p></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in;">
Operations Systems
Center (OSC) to develop a <i style="mso-bidi-font-style: normal;">voluntary</i>
“Notice of UAS Operations” submissions tool on Homeport. The objective is to
develop a communications network similar to New Orleans’. CG-FAC is also
working on a policy letter to provide guidance on the procedure for reporting
unauthorized UAS flights to include the FAA reporting guidelines.<a href="file:///C:/Users/lthom_000/Desktop/CG-FAC%202018%20Year%20in%20Review.docx#_edn5" name="_ednref5" style="mso-endnote-id: edn5;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "Calibri",sans-serif; font-size: 11.0pt; line-height: 107%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;">[5]</span></span><!--[endif]--></span></span></a><o:p></o:p></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in;">
<br /></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<b style="mso-bidi-font-weight: normal;">Rulemakings<o:p></o:p></b></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
This section contains an explanation of where we are (or are not) with
the TWIC reader final rule. Congress forbad the USCG from implementing the rule
or any similar rulemaking until an assessment of the TWIC program is reported
to Congress. The RAND Corporation is performing this assessment.<o:p></o:p></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in;">
Once completed
(estimated June 2019 by HSOAC/RAND), the Coast Guard will review the<o:p></o:p></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in;">
results of the
assessment and move forward with the TWIC Reader Rule implementation<o:p></o:p></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in;">
process, taking into
consideration any changes resulting from the assessment, coordination with the Transportation
Security Administration (TSA) and the Screening Coordination Office</div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in;">
<o:p></o:p></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in;">
(SCO), and any
possible Congressional feedback concerning the assessment.<span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "Calibri",sans-serif; font-size: 11.0pt; line-height: 107%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;"><a href="file:///C:/Users/lthom_000/Desktop/CG-FAC%202018%20Year%20in%20Review.docx#_edn6" style="mso-endnote-id: edn6;" title="">[6]</a></span></span><a href="file:///C:/Users/lthom_000/Desktop/CG-FAC%202018%20Year%20in%20Review.docx#_edn6" title=""><!--[endif]--></a></span></span><o:p></o:p></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in;">
<span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><span class="MsoEndnoteReference"><br /></span></span></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in;">
<o:p></o:p></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<b style="mso-bidi-font-weight: normal;">Policy Advisory Council (PAC)
Document Registry<o:p></o:p></b></div>
<div class="Default">
<span style="font-family: "Calibri",sans-serif; font-size: 11.0pt; mso-ascii-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;">PACs are “decision
documents…that provide interpretation of regulations covered under the Maritime
Transportation Security Act (MTSA) of 2002. PACs are a valuable tool for
explaining maritime security regulations and aiding Coast Guard field units and
the maritime industry.”<a href="file:///C:/Users/lthom_000/Desktop/CG-FAC%202018%20Year%20in%20Review.docx#_edn7" name="_ednref7" style="mso-endnote-id: edn7;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: Calibri, sans-serif; font-size: 11pt; line-height: 107%;">[7]</span></span><!--[endif]--></span></span></a>
PACs were issued from 2003 to 2011. Since then, these documents may have been superseded
or policy may have changed.<span style="mso-spacerun: yes;"> </span>The Coast
Guard reviewed all the PACS in 2017. <o:p></o:p></span></div>
<div class="Default" style="margin-left: .5in;">
<span style="font-family: "Calibri",sans-serif; font-size: 11.0pt; mso-ascii-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;">All active PACs were compiled into a single Adobe document that is
indexed and keyword searchable. PACs deemed “no longer required” were rescinded
and those incorporated into other policy documents were noted in the registry.
The new registry was published on Feb 6, 2018, replacing the individual PAC
files previously posted on Coast Guard’s Homeport website. The registry will be
reviewed by CG-FAC-2 on an annual basis, where updates and changes will be
tracked, noted in the registry, and communicated to port stakeholders through Homeport.<a href="file:///C:/Users/lthom_000/Desktop/CG-FAC%202018%20Year%20in%20Review.docx#_edn8" name="_ednref8" style="mso-endnote-id: edn8;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: Calibri, sans-serif; font-size: 11pt; line-height: 107%;">[8]</span></span><!--[endif]--></span></span></a><o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<b style="mso-bidi-font-weight: normal;">On the Horizon for 2019<o:p></o:p></b></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in;">
CG-FAC is working to
address Coast Guard specific tasking within the recent FAA<o:p></o:p></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in;">
Reauthorization Act,
which directs the Coast Guard, in coordination with other stakeholders, to establish a cyber
risk assessment model for the marine transportation system. This cyber risk assessment tool will
follow the National Institute of Standards and Technology’s Cybersecurity Framework, similar
to CG-FAC’s work on Cybersecurity Framework Profiles (CFP).<a href="file:///C:/Users/lthom_000/Desktop/CG-FAC%202018%20Year%20in%20Review.docx#_edn9" name="_ednref9" title=""><span class="MsoEndnoteReference"><span class="MsoEndnoteReference"><span style="font-family: "Calibri",sans-serif; font-size: 11.0pt; line-height: 107%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;">[9]</span></span></span></a></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in;">
<o:p></o:p></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in;">
<br /></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
What this section <i style="mso-bidi-font-style: normal;">doesn’t </i>mention:
issuance of two NVIC updates, 03-03 CH-3 and 03-07 CH-1. NVIC 03-07 CH-1 may be
waiting on the reader rule which means it is on the shelf depending on what
Congress says about the Rand report. NVIC 03-03 CH-3 has been worked on for
several years and should be ready to go?<o:p></o:p></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
Conclusion:<o:p></o:p></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
There is something for every MTSA stakeholder in this Office of Port and
Facility Compliance 2018 Year in Review. FSOs are urged to read the entire
report.<o:p></o:p></div>
<div class="MsoListParagraphCxSpFirst" style="line-height: normal; margin-bottom: .0001pt; margin: 0in; mso-add-space: auto;">
<br /></div>
<div class="MsoListParagraphCxSpMiddle" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-add-space: auto; text-indent: -.5in;">
<br /></div>
<div class="MsoListParagraphCxSpLast" style="line-height: normal; margin-bottom: .0001pt; margin: 0in; mso-add-space: auto;">
<br /></div>
<div style="mso-element: endnote-list;">
<!--[if !supportEndnotes]--><br clear="all" />
<hr align="left" size="1" width="33%" />
<!--[endif]-->
<div id="edn1" style="mso-element: endnote;">
<div class="MsoEndnoteText">
<span style="color: black;"><a href="file:///C:/Users/lthom_000/Desktop/CG-FAC%202018%20Year%20in%20Review.docx#_ednref1" name="_edn1" style="mso-endnote-id: edn1;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "Calibri",sans-serif; font-size: 10.0pt; line-height: 107%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;">[1]</span></span><!--[endif]--></span></span></a> U.S.
Department of Homeland Security. United States Coast Guard. Office of Port
& Facility Compliance. https://www.dco.uscg.mil/Our-Organization/Assistant-Commandant-for-Prevention-Policy-CG-5P/Inspections-Compliance-CG-5PC-/cgfac/<o:p></o:p></span></div>
</div>
<div id="edn2" style="mso-element: endnote;">
<div class="MsoEndnoteText">
<span style="color: black;"><a href="file:///C:/Users/lthom_000/Desktop/CG-FAC%202018%20Year%20in%20Review.docx#_ednref2" name="_edn2" style="mso-endnote-id: edn2;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "Calibri",sans-serif; font-size: 10.0pt; line-height: 107%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;">[2]</span></span><!--[endif]--></span></span></a>
U.S. Department of Homeland Security. United States Coast Guard. Office of Port
and Facility Compliance. <o:p></o:p></span></div>
<div class="MsoEndnoteText">
2018 Annual Report. 2019. <span style="mso-spacerun: yes;"> </span>https://www.dco.uscg.mil/Portals/9/CG-FAC/Documents/Year%20in%20Review/YearInReview2018.pdf?ver=2019-04-03-153641-730<o:p></o:p></div>
</div>
<div id="edn3" style="mso-element: endnote;">
<div class="MsoEndnoteText">
<span style="color: black;"><a href="file:///C:/Users/lthom_000/Desktop/CG-FAC%202018%20Year%20in%20Review.docx#_ednref3" name="_edn3" style="mso-endnote-id: edn3;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "Calibri",sans-serif; font-size: 10.0pt; line-height: 107%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;">[3]</span></span><!--[endif]--></span></span></a>Osburn,
Jennifer. Maritime Transportation Security Act of 2002 (MTSA) Effectiveness. 2017.
https://www.dco.uscg.mil/Portals/9/CG-FAC/Documents/MTSA%20Effectiveness.pdf?ver=2017-07-19-070242-347<o:p></o:p></span></div>
</div>
<div id="edn4" style="mso-element: endnote;">
<div class="MsoEndnoteText">
<span style="color: black;"><a href="file:///C:/Users/lthom_000/Desktop/CG-FAC%202018%20Year%20in%20Review.docx#_ednref4" name="_edn4" style="mso-endnote-id: edn4;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "Calibri",sans-serif; font-size: 10.0pt; line-height: 107%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;">[4]</span></span><!--[endif]--></span></span></a> U.S.
Department of Homeland Security. United States Coast Guard. Office of Port and
Facility Compliance. <o:p></o:p></span></div>
<div class="MsoEndnoteText">
2018 Annual Report. 2019.<span style="mso-spacerun: yes;"> </span>https://www.dco.uscg.mil/Portals/9/CG-FAC/Documents/Year%20in%20Review/YearInReview2018.pdf?ver=2019-04-03-153641-730<o:p></o:p></div>
</div>
<div id="edn5" style="mso-element: endnote;">
<div class="MsoEndnoteText">
<span style="color: black;"><a href="file:///C:/Users/lthom_000/Desktop/CG-FAC%202018%20Year%20in%20Review.docx#_ednref5" name="_edn5" style="mso-endnote-id: edn5;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "Calibri",sans-serif; font-size: 10.0pt; line-height: 107%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;">[5]</span></span><!--[endif]--></span></span></a>
Ibid.<o:p></o:p></span></div>
</div>
<div id="edn6" style="mso-element: endnote;">
<div class="MsoEndnoteText">
<span style="color: black;"><a href="file:///C:/Users/lthom_000/Desktop/CG-FAC%202018%20Year%20in%20Review.docx#_ednref6" name="_edn6" style="mso-endnote-id: edn6;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "Calibri",sans-serif; font-size: 10.0pt; line-height: 107%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;">[6]</span></span><!--[endif]--></span></span></a>
Ibid.<o:p></o:p></span></div>
</div>
<div id="edn7" style="mso-element: endnote;">
<div class="MsoEndnoteText">
<span style="color: black;"><a href="file:///C:/Users/lthom_000/Desktop/CG-FAC%202018%20Year%20in%20Review.docx#_ednref7" name="_edn7" style="mso-endnote-id: edn7;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "Calibri",sans-serif; font-size: 10.0pt; line-height: 107%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;">[7]</span></span><!--[endif]--></span></span></a> Ibid.<o:p></o:p></span></div>
</div>
<div id="edn8" style="mso-element: endnote;">
<div class="MsoEndnoteText">
<span style="color: black;"><a href="file:///C:/Users/lthom_000/Desktop/CG-FAC%202018%20Year%20in%20Review.docx#_ednref8" name="_edn8" style="mso-endnote-id: edn8;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "Calibri",sans-serif; font-size: 10.0pt; line-height: 107%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;">[8]</span></span><!--[endif]--></span></span></a>
Ibid.<o:p></o:p></span></div>
</div>
<div id="edn9" style="mso-element: endnote;">
<div class="MsoEndnoteText">
<span style="color: black;"><a href="file:///C:/Users/lthom_000/Desktop/CG-FAC%202018%20Year%20in%20Review.docx#_ednref9" name="_edn9" style="mso-endnote-id: edn9;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "Calibri",sans-serif; font-size: 10.0pt; line-height: 107%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;">[9]</span></span><!--[endif]--></span></span></a>
Ibid.<o:p></o:p></span></div>
</div>
</div>
<br />Laurie Thomashttp://www.blogger.com/profile/16611719448125721800noreply@blogger.com0tag:blogger.com,1999:blog-1555376450970352963.post-49200771958082164762019-03-30T18:05:00.001-07:002019-04-01T10:42:49.453-07:00Coast Guard Issues Final Rule on Seafarers' Access to Maritime Facilities<br />
<div class="MsoNormal">
<span style="font-family: "arial" , sans-serif;">On Monday April 1, 2019, the U.S Coast Guard
will issue the Final Rule on Seafarers Access to Maritime Facilities at <a href="https://www.govinfo.gov/content/pkg/FR-2019-04-01/pdf/2019-06272.pdf">https://www.govinfo.gov/content/pkg/FR-2019-04-01/pdf/2019-06272.pdf</a>.
The Federal Register section consists of a very enlightening preamble followed
by the actual sections of 33 CFR 105 that will be amended. <o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , sans-serif;">Here are some details
on the Final Rule. All quotations are from the Rule.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , sans-serif;"><br /></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<b style="mso-bidi-font-weight: normal;"><span style="font-family: "arial" , sans-serif;">What?</span></b><span style="font-family: "arial" , sans-serif;"> All MTSA facilities must implement a system
providing seafarers, pilots, and representatives of seamen’s welfare and labor
organizations access<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<br /></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<b style="mso-bidi-font-weight: normal;"><span style="font-family: "arial" , sans-serif;">Where?</span></b><span style="font-family: "arial" , sans-serif;"> Between vessels moored at the facility
and the facility gate<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<br /></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<b style="mso-bidi-font-weight: normal;"><span style="font-family: "arial" , sans-serif;">How?</span></b><span style="font-family: "arial" , sans-serif;"> In a timely manner and at no cost to
the seafarer or other individuals.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<br /></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<b style="mso-bidi-font-weight: normal;"><span style="font-family: "arial" , sans-serif;">What are the timelines?</span></b><span style="font-family: "arial" , sans-serif;"> The Final Rule is effective May 01, 2019. The new Sec. 21 of the Facility Security
Plan (FSP), System for Seafarers Access, needs to be submitted to the Coast
Guard for review by 02/01/2020, for implementation by 06/01/2020. Most
facilities are already in compliance with granting seafarer’s access, but may
not be meeting all the specific requirements of the Rule. Note: please talk to
your petty officer before submitting. Depending on when your FSP needs to be
annually inspected or re-approved, the Coast Guard may want you to submit this
section in alignment with the annual compliance review or reapproval process,
for Coast Guard workload considerations.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<br /></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<b style="mso-bidi-font-weight: normal;"><span style="font-family: "arial" , sans-serif;">The amendments to 33 CFR
105 are included at the end of this post.<o:p></o:p></span></b></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<br /></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<b style="mso-bidi-font-weight: normal;"><span style="font-family: "arial" , sans-serif;">Why did this regulatory
action come about? </span></b><span style="font-family: "arial" , sans-serif;">The
Seaman’s Church Institute tracked and documented a troubling pattern of
restrictions on access for seafarers and seafarer welfare providers over a
period of years. <span style="mso-spacerun: yes;"> </span>Despite actions on the
part of the Coast Guard to ensure resolution of access problems short of
regulation, access continued to be restricted. Congress took notice and Sec.
811 was included in the Coast Guard Authorization Act of 2010 (Pub. L. 111-281)
requiring “facility owners and operators to ensure shore access for seafarers
and other individuals. Specifically, section 811 requires each MTSA-regulated
facility to ‘‘provide a </span><span style="font-family: "arial" , sans-serif;">system for seamen assigned to a vessel at that facility,
pilots, and representatives of seamen’s welfare and labor organizations to
board and depart the vessel through the facility in a </span><span style="font-family: "arial" , sans-serif;">timely manner at no cost to the individual.’’ A Notice of Proposed
Rule Making (NPRM) published in 2014 resulted. The Coast Guard held a public
meeting on the issues in Washington, D.C. in early 2015.The comment period on
the NPRM closed in February 2015 but the Coast Guard reopened and extended the
comment period for an additional 60 days.</span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<br /></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<b style="mso-bidi-font-weight: normal;"><span style="font-family: "arial" , sans-serif;">More details:<o:p></o:p></span></b></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<br /></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<b style="mso-bidi-font-weight: normal;"><span style="font-family: "arial" , sans-serif;">Who is the ‘seafarer” and
who are<span style="mso-spacerun: yes;"> </span>the people who need to be given
access?</span></b><span style="font-family: "arial" , sans-serif;"> Seafarers are seafarers
assigned to a vessel at that facility. Only foreign seafarers who have proper
visa credentialing are affected by this rule. The NPRM considered family
members to be among the persons to be given access.<span style="mso-spacerun: yes;"> </span>This class of people has been eliminated in
the final rule. The persons to be given access are pilots and representatives
of seamen’s welfare and labor organizations.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<br /></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<b style="mso-bidi-font-weight: normal;"><span style="font-family: "arial" , sans-serif;">How is this access to be
accomplished?</span></b><span style="font-family: "arial" , sans-serif;"> By using
one of these methods:<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<br /></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(1)
Regularly scheduled escort between the vessel and the facility gate that
conforms to the vessel’s watch schedule as agreed upon between the vessel and
facility.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(2) An
on-call escort between the vessel and the facility gate.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(3)
Arrangements with taxi services or other transportation services, ensuring<span style="mso-spacerun: yes;"> </span>that any costs for providing the access described
in this section, above the service’s standard fees charged to any </span><span style="font-family: "arial" , sans-serif;">customer,
are not charged to the individual to whom such access is provided. If a
facility </span><span style="font-family: "arial" , sans-serif;"> </span><span style="font-family: "arial" , sans-serif;">provides arrangements with taxi
services or other transportation services as the only method for providing the
access described in this section, the facility is responsible to pay any fees
for transit within the facility.</span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(4)
Arrangements with seafarers’ welfare organizations to facilitate the access
described in this section.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(5)
Monitored pedestrian access routes between the vessel and facility gate.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(6) A
method, other than those in paragraphs (d)(1) through (5) of this section,
approved by the COTP.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(7) If
an access method relies on a third party, a back-up access method that will be
used if the third party is unable to or does not provide the required access in
any instance. An owner or operator must ensure that the access required in
paragraph (a) of this section is actually provided in all instances.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<br /></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<b style="mso-bidi-font-weight: normal;"><span style="font-family: "arial" , sans-serif;">What is “in a timely
manner”?</span></b><span style="font-family: "arial" , sans-serif;"> The Captain of
the Port (COTP) will decide if the manner is timely.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">The
facility owner or operator must provide the access described in this section
without </span><span style="font-family: "arial" , sans-serif;">unreasonable
delay, subject to review by the Captain of the Port (COTP). The facility owner
or operator must consider the following when establishing timely access without
unreasonable delay:</span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(1)
Length of time the vessel is in port.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(2)
Distance of egress/ingress between the vessel and facility gate.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(3) The
vessel watch schedules.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(4) The
facility’s safety and security procedures as required by law.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(5) Any
other factors specific to the vessel or facility that could affect access to
and from the vessel.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(d)
Access methods.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 22.5pt; margin-right: 0in; margin-top: 0in; mso-layout-grid-align: none; text-autospace: none;">
<br /></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<b style="mso-bidi-font-weight: normal;"><span style="font-family: "arial" , sans-serif;">What is “no cost”?</span></b><span style="font-family: "arial" , sans-serif;"> There is an excellent discussion of
this issue in the preamble to the Final Rule. “No cost” means two things: “no
cost to the seafarer” and also “no cost that is somehow underhandedly passed
onto the seafarer”, as in the facility bills the vessel for the costs of this
access who takes the cost out of the seafarers’ wages. On p. 12104 of the
Federal Register, there is a very stern notice about what the Coast Guard is
going to do if it finds out that fees as a condition of shoreside access are
being imposed on seafarers. <o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<br /></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">From the preamble, on costs:<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">The CGAA
does not specify who should pay for no-cost access for seafarers. Ultimately,
the Coast Guard determined that it is the facility’s responsibility to provide
the no cost service, as Coast Guard regulations already require each facility
to have an approved FSP, which must now include a system for providing no-cost
access to the facility for certain individuals.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">However,
the Coast Guard declined to specifically prohibit charges to the vessel, and
let parties decide the allocation of costs between facility and vessel. This
rule provides flexibility to facilities on how to comply with the mandate and
how to provide no-cost access for seafarers, as long as its solution does not
result in a cost to seafarers.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .25in; margin-right: 0in; margin-top: 0in; mso-layout-grid-align: none; text-autospace: none;">
<br /></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<b style="mso-bidi-font-weight: normal;"><span style="font-family: "arial" , sans-serif;">What must my new FSP Section
22, System for seafarers’ access, include?<o:p></o:p></span></b></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">On or
before February 3, 2020, the facility owner or operator must document the
facility’s system for providing the access described in this section in the
approved FSP in </span><span style="font-family: "arial" , sans-serif;">accordance
with § 105.410 or § 105.415.</span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">The
description of the facility’s system must include—<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(1)
Location of transit area(s) used for providing the access described in this section;<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(2)
Duties and number of facility personnel assigned to each duty associated with
providing the access described in this section;<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(3)
Methods of escorting and/or monitoring individuals transiting through the
facility;<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(4)
Agreements or arrangements between the facility and private parties, nonprofit
organizations, or other parties, to facilitate the access described in this section;
and<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(5)
Maximum length of time an individual would wait for the access described in
this section, based on the provided access method(s).<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in; mso-layout-grid-align: none; text-autospace: none;">
<br /></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<b style="mso-bidi-font-weight: normal;"><span style="font-family: "arial" , sans-serif;">What about TWIC and
seafarer access?<o:p></o:p></span></b></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<b style="mso-bidi-font-weight: normal;"><span style="font-family: "arial" , sans-serif;"><span style="mso-tab-count: 1;"> </span></span></b><span style="font-family: "arial" , sans-serif;">From
the preamble:<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">….</span><span style="font-family: "melior" , serif; font-size: 9.0pt;">
</span><span style="font-family: "arial" , sans-serif;">this rule does not change existing
TWIC requirements, and whether escorts are or are not required under TWIC rules
does not affect the obligation to provide no-cost access to the seafarer. The
facility has flexibility to decide how to comply with its TWIC </span><span style="font-family: "arial" , sans-serif;">requirements
and the no-cost access requirements of this rule…</span><span style="font-family: "melior" , serif; font-size: 9pt;"> </span><span style="font-family: "arial" , sans-serif;">Congress requires MTSA-regulated facilities
to grant access through the facility to seafarers at no cost to the seafarer.
This rule does not change the requirement to escort or otherwise monitor the
access of a person who is not authorized to have unescorted access to the
facility.</span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in; mso-layout-grid-align: none; text-autospace: none;">
<br /></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<b style="mso-bidi-font-weight: normal;"><span style="font-family: "arial" , sans-serif;">What about safety concerns
when granting this access?<o:p></o:p></span></b></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">From the preamble:<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">“This final rule provides facility owners and operators
with flexibility to ensure the safe passage of seafarers to and from the</span><span style="font-family: "melior" , serif; font-size: 9.0pt;">
</span><span style="font-family: "arial" , sans-serif;">facilities’ gates through a
variety of methods. It remains the responsibility of the facility owner or
operator to ensure safety in accordance with the approved </span><span style="font-family: "arial" , sans-serif;">FSP on file. If conditions are unsafe or overly burdensome
at certain facilities, mariners are encouraged to contact the local COTP to
report such unsafe or overly burdensome conditions.”</span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<br /></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<b style="mso-bidi-font-weight: normal;"><span style="font-family: "arial" , sans-serif;">What about facilities
operating under an Alternate Security Program (ASP)?<o:p></o:p></span></b></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">From the preamble:<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">“Each facility operating under a Coast Guard-approved ASP
must include seafarer access as directed by the ASP itself. This may be in the
form of an annex or appendix explaining how the </span><span style="font-family: "arial" , sans-serif;">facility will comply with this rule. This document must be
submitted to and approved by the cognizant COTP in the location of the facility
submitting the annex.”</span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<br /></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<br /></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<br /></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<b><span style="font-family: "arial" , sans-serif;">PART 105—MARITIME SECURITY: FACILITIES<o:p></o:p></span></b></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">■ 1. The authority citation for part 105 is revised to read
as follows:<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<b><span style="font-family: "arial" , sans-serif;">Authority: </span></b><span style="font-family: "arial" , sans-serif;">33 U.S.C. 1226, 1231; 46 U.S.C. 70103;
50 U.S.C. 191; Sec. 811, Pub. L. 111–<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">281, 124 Stat. 2905; 33 CFR 1.05–1, 6.04–11, 6.14, 6.16,
and 6.19; Department of<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">Homeland Security Delegation No. 0170.1.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<b><span style="font-family: "arial" , sans-serif;">§ 105.200 [Amended]<o:p></o:p></span></b></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">■ 2. Amend § 105.200 as follows:<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">■ a. In paragraph (b)(1), remove the words ‘‘security
organizational structure’’ and add in their place the words ‘‘organizational
structure of the security personnel’’ and remove the words ‘‘within that
structure’’;<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">■ b. In paragraph (b)(4), remove the text ‘‘an FSP’’ and
add in its place the text ‘‘a Facility Security Plan (FSP)’’;<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">■ c. In paragraph (b)(6) introductory text, remove the
acronym ‘‘TWIC’’ and add in its place the words ‘‘Transportation Worker
Identification Credential (TWIC)’’;<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">■ d. In paragraph (b)(6)(i), after the words ‘‘FSP are
permitted to’’ add the words ‘‘serve as an’’;<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">■ e. In paragraph (b)(6)(ii), remove the word ‘‘should’’
and add in its place the words ‘‘in the event that’’;<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">■ f. In paragraph (b)(6)(iii), remove the word ‘‘what’’,
and add in its place the word ‘‘which’’ and after the words ‘‘are secure areas
and’’ add the words ‘‘which are’’;<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">■ g. In paragraph (b)(9), remove the text ‘‘coordination
of’’ and add in its place the text ‘‘implementation of a system, in accordance
with § 105.237, coordinating’’ and remove the text<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">‘‘(including representatives of seafarers’ welfare and
labor organizations)’’ and add in its place the text ‘‘, as described in §
105.237(b)(3)’’; and<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">■ h. In paragraph (b)(14), remove the text ‘‘TSA’’ and add
in its place the text ‘‘Transportation Security Administration (TSA)’’.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">■ 3. Add § 105.237 to read as follows:<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<b><span style="font-family: "arial" , sans-serif;">§ 105.237 System for seafarers’ access.<o:p></o:p></span></b></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(a) <i>Access required. </i>Each facility owner or operator
must implement a system by June 1, 2020 for providing access through the
facility that enables individuals to transit to and from a<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">vessel moored at the facility and the facility gate in
accordance with the requirements in this section. The system must provide
timely access as described in paragraph (c) of this section and incorporate the
access methods described in paragraph (d) of this section at no cost to the
individuals covered. The system must comply with the Transportation Worker Identification
Credential (TWIC) provisions in this part.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(b) <i>Individuals covered. </i>The individuals to whom the
facility owner or operator must provide the access described in this section
include—<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(1) Seafarers assigned to a vessel at that facility;<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(2) Pilots; and<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(3) Representatives of seafarers’ welfare and labor
organizations.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(c) <i>Timely access. </i>The facility owner or operator
must provide the access described in this section without unreasonable delay,
subject to review by the Captain of the Port (COTP). The </span><span style="font-family: "arial" , sans-serif;">facility owner or operator must consider the following when
establishing timely access without unreasonable delay:</span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(1) Length of time the vessel is in port.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(2) Distance of egress/ingress between the vessel and
facility gate.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(3) The vessel watch schedules.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(4) The facility’s safety and security procedures as
required by law.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(5) Any other factors specific to the vessel or facility
that could affect access to and from the vessel.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(d) <i>Access methods. </i>The facility owner or operator
must ensure that the access described in this section is provided through one
or more of the following methods:<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(1) Regularly scheduled escort between the vessel and the
facility gate that conforms to the vessel’s watch schedule as agreed upon
between the vessel and facility.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(2) An on-call escort between the vessel and the facility
gate.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(3) Arrangements with taxi services or other transportation
services, ensuring that any costs for providing the access described in this
section, above the service’s standard fees charged to any </span><span style="font-family: "arial" , sans-serif;">customer, are not charged to the individual to whom such
access is provided. If a facility provides arrangements with taxi services or
other transportation services as the only method for providing the access described
in this section, the facility is responsible to pay any fees for transit within
the facility.</span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(4) Arrangements with seafarers’ welfare organizations to
facilitate the access described in this section.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(5) Monitored pedestrian access routes between the vessel
and facility gate.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(6) A method, other than those in paragraphs (d)(1) through
(5) of this section, approved by the COTP.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(7) If an access method relies on a third party, a back-up
access method that will be used if the third party is unable to or does not
provide the required access in any instance. An owner or operator must ensure
that the access required in paragraph (a) of this section is actually provided
in all instances.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(e) <i>No cost to individuals. </i>The facility owner or
operator must provide the access described in this section at no cost to the
individual to whom such access is provided.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(f) <i>Described in the Facility Security Plan (FSP). </i>On
or before February 3, 2020, the facility owner or operator must document the
facility’s system for providing the access described in this </span><span style="font-family: "arial" , sans-serif;">section in the approved FSP in accordance with § 105.410 or
§ 105.415.</span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">The description of the facility’s system must include—<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(1) Location of transit area(s) used for providing the
access described in this section;<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(2) Duties and number of facility personnel assigned to
each duty associated with providing the access described in this section;<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(3) Methods of escorting and/or monitoring individuals
transiting through the facility;<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(4) Agreements or arrangements between the facility and
private parties, nonprofit organizations, or other parties, to facilitate the
access described in this<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">section; and <o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(5) Maximum length of time an individual would wait for the
access described in this section, based on the provided access method(s).<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">■ 4. Amend § 105.405 as follows:<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">■ a. In paragraph (a)(18), remove the text ‘‘part 105;
and,’’ and add in its place ‘‘this part;’’;<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">■ b. In paragraph (a)(21), remove the period at the end of
the paragraph and add in its place ‘‘; and’’; and<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">■ c. Add paragraph (a)(22).<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">The addition reads as follows:<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<b><span style="font-family: "arial" , sans-serif;">§ 105.405 Format and content of the Facility
Security Plan (FSP).<o:p></o:p></span></b></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(a) * * *<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">(22) System for seafarers’ access.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">* * * * *<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<span style="font-family: "arial" , sans-serif;">Dated: March 27, 2019.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<b><span style="font-family: "arial" , sans-serif;">Jennifer F. Williams,<o:p></o:p></span></b></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<i><span style="font-family: "arial" , sans-serif;">Captain, U. S. Coast Guard, Director of<o:p></o:p></span></i></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<i><span style="font-family: "arial" , sans-serif;">Inspections and Compliance.<o:p></o:p></span></i></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-layout-grid-align: none; text-autospace: none;">
<br /></div>
<br />Laurie Thomashttp://www.blogger.com/profile/16611719448125721800noreply@blogger.com0tag:blogger.com,1999:blog-1555376450970352963.post-51094014111994084062019-02-12T13:56:00.000-08:002019-02-12T13:56:13.783-08:00DHS Science and Technology Directorate (S&T) has Issued a New Request for Comment, Assessing the Risk-Mitigation Value of TWIC® at Maritime Facilities. <br />
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">On Feb. 07, 2019, Science and Technology Directorate
(S&T), Department of Homeland Security (DHS) issued a new request for
comment, Assessing the Risk-Mitigation Value of TWIC® at Maritime Facilities.<span style="mso-spacerun: yes;"> </span>This notice is located in the Federal
Register at https://www.govinfo.gov/content/pkg/FR-2019-02-07/pdf/2019-01377.pdf
. <o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">Please note that this notice requests comments on two items:
number one, how effective the TWIC program is at enhancing security and
reducing security risks for regulated maritime facilities and vessels, and
number two, specific issues concerning an annual information collection about assessing
the risk mitigation value of TWIC® at maritime facilities. <o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">From the notice:<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-left: .5in;">
<span style="font-family: Arial, Helvetica, sans-serif;">By law, the Secretary of Homeland
Security is required to commission an assessment of how effective the
transportation security card program is at enhancing security and reducing
security risks for regulated maritime facilities and vessels. Through the
transportation security card program, the Department issues the Transportation
Worker Identification Credential (TWIC®). Legislation passed August 2, 2018
restricts the U.S. Coast Guard (USCG) from implementing any rule requiring the
use of biometric readers for TWIC® until after submission to Congress of the
results of this effectiveness assessment.<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-left: .5in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal" style="margin-left: .5in;">
<span style="font-family: Arial, Helvetica, sans-serif;">The Homeland Security Operational Analysis
Center (HSOAC), a federally funded research and development center operated by
the RAND Corporation, will collect information from those involved in maritime security
on behalf of the DHS S&T Research and Development Partnerships (RDP)
Federally Funded Research and Development Center (FFRDC) Program Management
Office. HSOAC will visit regulated maritime facilities and terminals and
conduct interviews using a semi-structured interview method to collect
information. HSOAC will analyze this information and use it to produce a public
report with its research findings.<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-left: .5in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal" style="margin-left: .5in;">
<span style="font-family: Arial, Helvetica, sans-serif;">DATES: Comments are encouraged and accepted
until April 8, 2019.<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-left: .5in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal" style="margin-left: .5in;">
<span style="font-family: Arial, Helvetica, sans-serif;">ADDRESSES: You may submit comments,
identified by docket number DHS–2018–0052, at:<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-left: .5in;">
<span style="font-family: Arial, Helvetica, sans-serif;">• Federal eRulemaking Portal:
http://www.regulations.gov. Please follow the instructions for submitting
comments.<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-left: .5in;">
<span style="font-family: Arial, Helvetica, sans-serif;">• Mail and hand delivery or commercial
delivery: Science and Technology Directorate, ATTN: Chief Information
Office—Mary Cantey, 245 Murray Drive, Mail Stop 0202, Washington, DC 20528.<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-left: .5in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal" style="margin-left: .5in;">
<span style="font-family: Arial, Helvetica, sans-serif;">Instructions: All submissions
received must include the agency name and docket number DHS–2018–0052.<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-left: .5in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal" style="margin-left: .5in;">
<span style="font-family: Arial, Helvetica, sans-serif;">SUPPLEMENTARY INFORMATION: The Secretary
of Homeland Security, according to Public Law 114–278, is required to
commission an assessment of how effective the transportation security card
program is at enhancing security and reducing security risks for regulated
maritime facilities and vessels. Through the transportation security card
program, the Department issues the Transportation Worker Identification
Credential (TWIC®). In addition, Public Law 115–230 restricts the USCG from
implementing any rule requiring the use of biometric readers for TWIC® until
submitting the results of this assessment to Congress. DHS, in accordance with
the Paperwork Reduction Act (PRA), 44 U.S.C. 3501 et seq., provides the general
public and Federal agencies with an opportunity to comment on proposed, revised,
and continuing collections of information. DHS is soliciting comments on the
proposed information collection request (ICR) that is described below. DHS is
especially interested in public comment addressing the following issues: (1) Is
this collection necessary to the proper functions of the Department; (2) will
this information be processed and used in a timely manner; (3) is the estimate
of burden accurate; (4) how might the Department enhance the quality, utility,
and clarity of the information to be collected; and (5) how might the
Department minimize the burden of this collection on the respondents, including
through the use of information technology? Please note that written comments
received in response to this notice will be considered public records.<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-left: .5in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal" style="margin-left: .5in;">
<span style="font-family: Arial, Helvetica, sans-serif;">Title of Collection: Assessing the
Risk Mitigation Value of TWIC® at Maritime Facilities.<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-left: .5in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal" style="margin-left: .5in;">
<span style="font-family: Arial, Helvetica, sans-serif;">Type of Review: New.<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-left: .5in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal" style="margin-left: .5in;">
<span style="font-family: Arial, Helvetica, sans-serif;">Affected Public: Port security
subject matter experts such as Port Authority Security Managers, Facility
Security Managers, Industry Security Managers, and local law enforcement;
Labor, Other Industry Operation and Technology Managers.<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-left: .5in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal" style="margin-left: .5in;">
<span style="font-family: Arial, Helvetica, sans-serif;">Frequency of Collection: Once, Annually.<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-left: .5in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal" style="margin-left: .5in;">
<span style="font-family: Arial, Helvetica, sans-serif;">Average Burden per Response: 60 minutes.<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-left: .5in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal" style="margin-left: .5in;">
<span style="font-family: Arial, Helvetica, sans-serif;">Estimated Number of Annual Responses:
400.<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-left: .5in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal" style="margin-left: .5in;">
<span style="font-family: Arial, Helvetica, sans-serif;">Total Annual Burden Hours: 400.<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-left: .5in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal" style="margin-left: .5in;">
<br /></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><b>Discussion:</b> There is an effective and an ineffective way to comment on a
regulation. From “Tips for Submitting Effective Comments”, found at <a href="https://www.regulations.gov/docs/Tips_For_Submitting_Effective_Comments.pdf">https://www.regulations.gov/docs/Tips_For_Submitting_Effective_Comments.pdf</a>:<o:p></o:p></span></div>
<div class="MsoListParagraphCxSpFirst" style="mso-list: l0 level1 lfo1; text-indent: -.25in;">
</div>
<span style="font-family: Arial, Helvetica, sans-serif;">·<span style="font-size: 7pt; font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal;"> "</span>Read and understand the regulatory document you
are commenting on<br />·<span style="font-size: 7pt; font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal;">
</span>Feel free to reach out to the agency with
questions<br />·<span style="font-size: 7pt; font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal;">
</span>Be concise but support your claims<br />·<span style="font-size: 7pt; font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal;">
</span>Base your justification on sound reasoning,
scientific evidence, and/or how you will be impacted<br />·<span style="font-size: 7pt; font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal;">
</span>Address trade-offs and opposing views in your
comment<br />·<span style="font-size: 7pt; font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal;">
</span>There is no minimum or maximum length for an
effective comment<br />·<span style="font-size: 7pt; font-stretch: normal; font-variant-east-asian: normal; font-variant-numeric: normal; line-height: normal;">
</span>The comment process is not a vote – one well
supported comment is often more influential than a thousand form letters."</span><div>
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span><div class="MsoListParagraphCxSpMiddle">
<span style="font-family: Arial, Helvetica, sans-serif;"><o:p></o:p></span></div>
<div class="MsoListParagraphCxSpMiddle" style="margin-left: 0in; mso-add-space: auto;">
<span style="font-family: Arial, Helvetica, sans-serif;">Comments
submitted to address the first issue need to mention how the program does or
does not enhance security and reduce security risks for regulated maritime
facilities and vessels. That you are personally inconvenienced during the
enrollment process or that the cards are not accepted at airports probably does
not address the question of risk reduction in the maritime environment. A
comment that is submitted without the word “risk” or “security” in it seems to
me to be flawed at the onset. DHS is required to consider these comments so
this is one more chance for us to get our hands on the TWIC program and
influence its path. Let’s make sure we don’t waste this opportunity.<o:p></o:p></span></div>
<div class="MsoListParagraphCxSpMiddle" style="margin-left: 0in; mso-add-space: auto;">
<br /></div>
<div class="MsoListParagraphCxSpMiddle" style="margin-left: 0in; mso-add-space: auto;">
<span style="font-family: Arial, Helvetica, sans-serif;">I
am still gathering information on the details of number two, the information
collection. I want to know how DHS arrived at the figure of 400 persons who
will submit information, and that the collection will take one hour. Until I
know these details, I can’t sensibly comment on the second issue.<o:p></o:p></span></div>
<div class="MsoListParagraphCxSpMiddle">
<br /></div>
<div class="MsoListParagraphCxSpLast" style="margin-left: 0in; mso-add-space: auto;">
<br /></div>
<br /></div>
Laurie Thomashttp://www.blogger.com/profile/16611719448125721800noreply@blogger.com0tag:blogger.com,1999:blog-1555376450970352963.post-17195632947543765512019-01-18T07:13:00.002-08:002019-01-18T07:13:27.583-08:00Status of TWIC Enrollment Services During Shutdown<span class="ember-view" id="ember1117" style="background: 0px 0px rgb(255, 255, 255); border: 0px; box-sizing: inherit; color: rgba(0, 0, 0, 0.75); font-family: -apple-system, system-ui, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", "Fira Sans", Ubuntu, Oxygen, "Oxygen Sans", Cantarell, "Droid Sans", "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Emoji", "Segoe UI Symbol", "Lucida Grande", Helvetica, Arial, sans-serif; font-size: 14px; line-height: inherit !important; margin: 0px; outline: 0px; padding: 0px; vertical-align: baseline; white-space: pre-wrap;"><span style="background: 0px 0px; border: 0px; box-sizing: inherit; line-height: inherit !important; margin: 0px; outline: 0px; padding: 0px; vertical-align: baseline;">I am getting a lot of questions from my fellow FSOs about the status of TWIC enrollment centers during the shutdown. Here's the word from TSA:
"This message is a notice to stakeholders about the lapse in Federal funding. The Transportation Security Administration’s (TSA) TWIC® enrollment services are still open and operating and in-person appointments are available.* If you require assistance with enrollment services, please call 855-DHS-UES1 (855-347-8371) between 8:00am - 10:00pm Eastern, Mon. - Fri.
Additionally, the issuance/delivery of the TWIC® card is not impacted. With the exception to applicants subject to redress, eligible TWIC® applicants should expect to receive a TWIC® card in approximately 4 to 14 days, pending delivery times.
For additional information on the TSCC or TWIC®, please contact: </span></span><a class="ember-view" href="mailto:TWIC.issue@tsa.dhs.gov" id="ember1121" rel="noopener noreferrer" style="background: 0px 0px rgb(255, 255, 255); border: 0px; box-sizing: inherit; font-family: -apple-system, system-ui, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", "Fira Sans", Ubuntu, Oxygen, "Oxygen Sans", Cantarell, "Droid Sans", "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Emoji", "Segoe UI Symbol", "Lucida Grande", Helvetica, Arial, sans-serif; font-size: 14px; font-weight: 600; line-height: inherit !important; margin: 0px; padding: 0px; text-decoration-line: none; touch-action: manipulation; vertical-align: baseline; white-space: pre-wrap;" target="_blank">TWIC.issue@tsa.dhs.gov</a><span class="ember-view" id="ember1125" style="background: 0px 0px rgb(255, 255, 255); border: 0px; box-sizing: inherit; color: rgba(0, 0, 0, 0.75); font-family: -apple-system, system-ui, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", "Fira Sans", Ubuntu, Oxygen, "Oxygen Sans", Cantarell, "Droid Sans", "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Emoji", "Segoe UI Symbol", "Lucida Grande", Helvetica, Arial, sans-serif; font-size: 14px; line-height: inherit !important; margin: 0px; outline: 0px; padding: 0px; vertical-align: baseline; white-space: pre-wrap;"><span style="background: 0px 0px; border: 0px; box-sizing: inherit; line-height: inherit !important; margin: 0px; outline: 0px; padding: 0px; vertical-align: baseline;">."</span></span>Laurie Thomashttp://www.blogger.com/profile/16611719448125721800noreply@blogger.com0tag:blogger.com,1999:blog-1555376450970352963.post-36133875735214947192019-01-15T07:47:00.000-08:002019-01-15T07:49:12.251-08:00<br />
<div align="center" class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in; text-align: center;">
<b style="mso-bidi-font-weight: normal;">A Summary of Department of Homeland Security Office of Inspector General (OIG) Report
OIG-19-16, DHS’ and TSA’s Compliance with Public Law 114-278<o:p></o:p></b></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
Please note:
The opinions in this post are solely the author’s and do not reflect the
opinion of the University of Findlay or anyone’s opinion but the author’s.<o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
On Dec. 14,
2018 the Department of Homeland Security Office of Inspector General (OIG)
published OIG-19-16, DHS’ and TSA’s Compliance with Public Law 114-278<a href="file:///C:/Users/lthom_000/Desktop/OIG%20post.docx#_edn1" name="_ednref1" style="mso-endnote-id: edn1;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "calibri" , sans-serif; font-size: 11.0pt; line-height: 107%;">[1]</span></span><!--[endif]--></span></span></a>,
Transportation Security Card Program Assessment. This audit was performed to
determine DHS’ and TSA’s conformity with the public law’s requirements. P.L.
114-278 required the two agencies to undertake actions to improve the TWIC vetting
process, and to conduct an overall assessment of the TWIC program effectiveness.
The words “audit” and “report” are used interchangeably and designate the
findings related in 19-16.<o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
The law has
four sections:<o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
(a)
Credential Improvements <o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
(b) Comprehensive
Security Assessment of the Transportation Security Card Program<o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
(c) Corrective
Action Plan; Program Reforms<o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
(d) Inspector
General Review<o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
Actions that
TSA were required to undertake to improve the vetting process/credential
improvements (section a) include a risk analysis of the TWIC security threat
assessment; implementing additional internal controls and best practices; improving
fraud detection techniques; updating the guidance provided to Trusted Agents
(TAs) regarding the vetting process and related regulations; finalizing a
manual for Trusted Agents and adjudicators on the vetting process, and
establishing quality controls for consistency in adjudication decisions. <o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
The overall
effectiveness review (section b) includes an evaluation of both the
credentialing and the renewal process. It also includes a detailed analysis of
the security value of the program, by evaluating the extent to which the program
addresses security risks in the maritime environment; by evaluating the
possibility of non-biometric credential alternatives; by identifying the
technology, business process, and operational impacts of the use of the TWIC
card and readers; by assessing the costs and benefits of the program; and
evaluating the extent to which DHS has addressed the deficiencies in the
Program identified by the Government Accountability Office (GAO) and the OIG before
the date of enactment of the law. The risk analysis of the security threat
assessment and the overall effectiveness review were awarded the Homeland
Security Operational Analysis Center (HSOAC), operated by the RAND Corporation.<o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
The assessment
mandated under the law was to have begun in February 2017 and be completed in a
year, with the results submitted to Congress in April 2018.<o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
Two months
after the date on which the assessment was completed, DHS was supposed to
submit to Congress a corrective action plan addressing any deficiencies. The
law required the DHS OIG to evaluate TSA’s implementation of the actions required
by the law and submit a report to Congress no later than December 16,
2018.<span style="mso-spacerun: yes;"> </span>Please note: a complete text of
P.L. 114-278 is included in this post under footnote 1.<o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
The OIG’s
report 19-16 evaluates DHS’ compliance with the requirements of P.L. 144-278.
The report contains some very alarming (and sometimes hard to believe) language.<span style="mso-spacerun: yes;"> </span>Persons who are affected by the TWIC program should
read the entire report.<span style="mso-spacerun: yes;"> </span>Below are
highlights.<o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
There were
six actions that TSA was required to perform to improve the vetting process,
(a)(2) A – F. Although the OIG describes TSA as partly complying with A and B
ad complying with C – E, the report also states “We were not able to fully
address Congress’ requirement to evaluate TSA’s implementation of the required
actions identified in the public law because TSA is still in the process of
implementing elements of the required actions in the TWIC program. However, we
have concerns with aspects of TSA’s responses to all of the required actions.”<a href="file:///C:/Users/lthom_000/Desktop/OIG%20post.docx#_edn2" name="_ednref2" style="mso-endnote-id: edn2;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "calibri" , sans-serif; font-size: 11.0pt; line-height: 107%;">[2]</span></span><!--[endif]--></span></span></a>
The report then describes TSA’s compliance by each individual required action. <o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
In action B<i style="mso-bidi-font-style: normal;">, implementing additional internal controls</i>,
the report states “Until TSA addresses all 19 recommendations, it may be
overlooking vulnerabilities in the STA [security threat assessment] process and
opportunities to improve the TWIC program. This may result in individuals
obtaining TWIC cards who may pose a security risk to our Nation’s maritime
facilities and vessels.” The language under Action C, <i style="mso-bidi-font-style: normal;">improve fraud detection techniques</i>, is especially troubling.<span style="mso-spacerun: yes;"> </span>There is a subset of recommendations under
this required action.<span style="mso-spacerun: yes;"> </span>Under improving
fraud detection techniques by establishing benchmarks and a process for
electronic document verification, TSA implemented the birth verification
service as one of the fraud detection techniques; however, TSA uses it in a “limited
capacity.”<a href="file:///C:/Users/lthom_000/Desktop/OIG%20post.docx#_edn3" name="_ednref3" style="mso-endnote-id: edn3;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "calibri" , sans-serif; font-size: 11.0pt; line-height: 107%;">[3]</span></span><!--[endif]--></span></span></a>
Under the requirement that Trusted Agents (TA) receive annual training in fraud
detection,<span style="mso-spacerun: yes;"> </span>the OIG “was provided a copy
of the contract for enrollment services that requires annual training to
enhance the knowledge of TAs in identifying potentially fraudulent identity
documents.<a href="file:///C:/Users/lthom_000/Desktop/OIG%20post.docx#_edn4" name="_ednref4" style="mso-endnote-id: edn4;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "calibri" , sans-serif; font-size: 11.0pt; line-height: 107%;">[4]</span></span><!--[endif]--></span></span></a>”
A copy of a contract does not verify that training is being performed; it
merely indicates that someone has drawn up a contract and that someone else has
signed it. (Throughout this document, there is language that indicates that OIG
conducted this audit by high-level interviews and limited (if any) auditing in
the field. There is nothing in the methodology that indicates that the OIG went
into the field to confirm the HSOAC findings.) <o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
The final
comment on fraud detection needs to be reproduced in its entirety: <o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 27.0pt; margin-right: 0in; margin-top: 0in;">
Lastly, TSA also complied with the
requirement to review relevant security threat information provided by the TAs.
According to TSA, if TAs suspect a fraudulent document, they note their
concerns in the system for TSA’s Program Management Office to review. Even
though TAs may include comments about potential fraudulent documents, the
application process continues. If, following a review of the TA comments, TSA
confirms that fraudulent documents were used, it can take one of four actions
depending on the status of the applicant’s adjudication: stop the enrollment,
stop the credential’s production, pull the credential from the Enrollment
Center card batch, or cancel the TWIC card after production.<a href="file:///C:/Users/lthom_000/Desktop/OIG%20post.docx#_edn5" name="_ednref5" style="mso-endnote-id: edn5;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "calibri" , sans-serif; font-size: 11.0pt; line-height: 107%;">[5]</span></span><!--[endif]--></span></span></a><o:p></o:p></div>
<br />
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in; tab-stops: 0in;">
This seems to indicate that no matter how sloppily fraudulent the document
offered up by an enrollee to obtain a credential, the enrollment process must
go on.<o:p></o:p></div>
<br />
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
In reviewing
Action E<i style="mso-bidi-font-style: normal;">, finalize a manual for trusted agents
and adjudicators</i>, the audit states, “We still found the manual disorganized
and some guidance was duplicative, contradictory, and outdated. A disorganized
training manual with outdated policies, procedures, and guidance may hinder
adjudicators’ ability to make appropriate, timely, and consistent decisions.”<a href="file:///C:/Users/lthom_000/Desktop/OIG%20post.docx#_edn7" name="_ednref7" style="mso-endnote-id: edn7;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "calibri" , sans-serif; font-size: 11.0pt; line-height: 107%;">[7]</span></span><!--[endif]--></span></span></a><o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
In reviewing
Action F, <i style="mso-bidi-font-style: normal;">establish quality controls to
ensure consistent procedures to review adjudication decisions and terrorism
vetting decisions</i>, the OIG stated,<o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 22.5pt; margin-right: 0in; margin-top: 0in;">
Although TSA has QA SOPs [quality
assurance standard operating procedures] for both adjudication decisions and
terrorism vetting decisions, we could not test to verify whether TSA
consistently applied these quality assurance procedures in its reviews. We
found the QA SOPs did not contain sufficient details on all procedures, such as
a random sampling methodology for adjudication cases… Without consistent
procedures and quality controls in QA reviews, TSA may be missing errors made
by the adjudicators and terrorism vetting analysts. As a result, TSA may
inadvertently issue TWIC cards to individuals who might pose security risks to
our maritime transportation sector.<a href="file:///C:/Users/lthom_000/Desktop/OIG%20post.docx#_edn8" name="_ednref8" style="mso-endnote-id: edn8;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "calibri" , sans-serif; font-size: 11.0pt; line-height: 107%;">[8]</span></span><!--[endif]--></span></span></a><o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
TSA was a
year late submitting the required report on the overall effectiveness of the
program required in section (b) of the law. The reason for this delay: DHS
“experienced challenges identifying an office responsible for the effort.” The
assessment’s estimated completion date is April 27, 2019. <a href="file:///C:/Users/lthom_000/Desktop/OIG%20post.docx#_edn9" name="_ednref9" style="mso-endnote-id: edn9;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "calibri" , sans-serif; font-size: 11.0pt; line-height: 107%;">[9]</span></span><!--[endif]--></span></span></a>
Per the law, if the results of this assessment indicate deficiencies, a
corrective action plan needs to be implemented, but DHS has not designated a
point of contact to oversee preparation of this plan.<o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<b style="mso-bidi-font-weight: normal;">Discussion.</b><span style="mso-spacerun: yes;"> </span>I approach any document related to the TWIC
program from the perspective of a supporter of the program and of a security
services provider and Facility Security Officer for smaller facilities. Before
TWIC, we did not have a nationwide check, albeit a snapshot at the time of
enrollment, of the background of persons being granted unescorted access to
secure areas of regulated facilities and vessels. Larger ports and facilities
have a much wider array of tools in their toolkit to provide personnel security.
Many smaller facilities use the credential as a key layer of defense,
especially for threats involving non-employees. <o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
So, as a
supporter of the program, I am disturbed that the OIG described the training
manual for TAs as containing material that is contradictory and outdated. I am
disturbed by the possibility that DHS and TSA seem to have difficulty
designating a person responsible for the corrective action plan mandated by the
law. And I was very disturbed by the language stating that individuals who may
pose a risk to the nation’s marine terminals and vessels are being granted
credentials because of the identified<span style="mso-spacerun: yes;">
</span>shortcomings of the program; this language appears in several places in
the document.<o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
I am also
disturbed by the apparent lack of consequences for the problems identified in
this document. Because it contains no recommendations, DHS and TSA did not
provide any responses. DHS did not award a work order for the assessment for
more than a year after the deadline. As an FSO, if I am late for many regulatory
requirements – drills, exercises, security inspections, annual Facility
Security Plan (FSP) audits, TWIC renewals, five-year FSP approvals, to name
just a few – there are immediate and unpleasant consequences from the
regulators. The FSP language must be clear and concise – if it is contradictory
or outdated, as the OIG found the TSA manuals to be, the USCG petty officers
will let me know. Regulatory agencies like TSA and the wider DHS, however, seem
to be held to a different, sloppier standard. <o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
The problems
identified in the OIG report are described as having the capability of allowing
individuals to obtain TWIC cards who may pose a security risk to our Nation’s
maritime facilities and vessels. That’s the bad news. The good news is that P.L.
114-278 is in place to provide fixes/improvements for the TWIC program, and
contains the oversight provision that generated OIG 19-16. TSA is required to
perform actions immediately to improve the program (section a), and the OIG
looks over their shoulder to report compliance. The RAND corporation is
reporting on the security effectiveness of the program required in section b. (DHS
will eventually overcome their challenges in identifying who is responsible for
what.) Section c requires a corrective action plan, which the OIG will also
review. The mission of the OIG is to “provide independent oversight and promote
excellence, integrity, and accountability within DHS.”<a href="file:///C:/Users/lthom_000/Desktop/OIG%20post.docx#_edn10" name="_ednref10" style="mso-endnote-id: edn10;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "calibri" , sans-serif; font-size: 11.0pt; line-height: 107%;">[10]</span></span><!--[endif]--></span></span></a>
Sometimes accountability is achieved by revealing unpleasant truths, as OIG
19-16 does. <o:p></o:p></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal">
As a final thought, some other wider issues need to be
considered when reflecting on the problems raised by the OIG report. <span style="mso-spacerun: yes;"> </span>TSA has a major role in the TWIC program but
the agency’s main focus is on the aviation sector. Personnel distribution
within the agency confirms this. More than 43,000 transportation security
officers and more than 600 aviation transportation security inspectors ensure
security at the 440 federalized airports. <a href="file:///C:/Users/lthom_000/Desktop/OIG%20post.docx#_edn11" name="_ednref11" style="mso-endnote-id: edn11;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "calibri" , sans-serif; font-size: 11.0pt; line-height: 107%;">[11]</span></span><!--[endif]--></span></span></a>
Describing its multimodal security efforts, TSA states that it utilizes
approximately 250 surface transportation inspectors to conduct annual
inspections in support of risk-based security of more than 4 million miles of
roadways, nearly 140,000 miles of railroad track, approximately 612,000 bridges
and more than 470 tunnels, approximately 360 maritime ports, and approximately
2.75 million miles of pipeline.<a href="file:///C:/Users/lthom_000/Desktop/OIG%20post.docx#_edn12" name="_ednref12" style="mso-endnote-id: edn12;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "calibri" , sans-serif; font-size: 11.0pt; line-height: 107%;">[12]</span></span><!--[endif]--></span></span></a>
“TSA has an annual surface security operating budget of around $111 million,
which represents approximately 3 percent of TSA’s total budget, while the remainder
of the budget is dedicated primarily to aviation operations”, according to the
Government Accountability Office.<span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "calibri" , sans-serif; font-size: 11.0pt; line-height: 107%;"><a href="file:///C:/Users/lthom_000/Desktop/OIG%20post.docx#_edn13" style="mso-endnote-id: edn13;" title="">[13]</a></span></span><a href="file:///C:/Users/lthom_000/Desktop/OIG%20post.docx#_edn13" title=""><!--[endif]--></a></span></span>
<o:p></o:p></div>
<div class="MsoNormal">
<span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><span class="MsoEndnoteReference"><br /></span></span></span></div>
<div class="MsoNormal">
More critically, key people may not be in place at DHS or TSA
to make decisions, sign off on important documents, and generally oversee the
progress of important programs like TWIC. In August 2018, approximately 30% of
the top positions in DHS remained unfilled.<a href="file:///C:/Users/lthom_000/Desktop/OIG%20post.docx#_edn14" name="_ednref14" style="mso-endnote-id: edn14;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "calibri" , sans-serif; font-size: 11.0pt; line-height: 107%;">[14]</span></span><!--[endif]--></span></span></a>
Furthermore, the administration has chosen not to staff an essential White
House office responsible for personnel decisions. The White House Office of
Presidential Personnel<o:p></o:p></div>
<div class="MsoNormal" style="margin-left: 27.0pt;">
…oversees the selection process
for Presidential appointments and works to recruit candidates to serve the
President in departments and agencies throughout the Executive Branch.
Presidential Personnel staff present candidates for PAS [Presidential
Appointment needing Senate confirmation] positions to the Senate for
confirmation after they have been approved by the President and have gone
through Personnel’s selection and clearance process. Additionally, the office
is responsible for thousands of lower level appointees. <span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "calibri" , sans-serif; font-size: 11.0pt; line-height: 107%;"><a href="file:///C:/Users/lthom_000/Desktop/OIG%20post.docx#_edn15" style="mso-endnote-id: edn15;" title="">[15]</a></span></span><a href="file:///C:/Users/lthom_000/Desktop/OIG%20post.docx#_edn15" title=""><!--[endif]--></a></span></span><o:p></o:p></div>
<div class="MsoNormal" style="margin-left: 27.0pt;">
<span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><span class="MsoEndnoteReference"><br /></span></span></span></div>
<div class="MsoNormal">
In March 2018, <i style="mso-bidi-font-style: normal;">National
Review</i> described the White House personnel office: “Compared with President
Bill Clinton’s administration at a similar point in his presidency, Trump’s
personnel office has fewer than a fourth the number of staffers to process
paperwork and interview applicants. Several of the offices at the personnel
department are empty most of the day.” <a href="file:///C:/Users/lthom_000/Desktop/OIG%20post.docx#_edn16" name="_ednref16" style="mso-endnote-id: edn16;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "calibri" , sans-serif; font-size: 11.0pt; line-height: 107%;">[16]</span></span><!--[endif]--></span></span></a>There
is no evidence that this short-staffing has been remedied; there is evidence
that it is continuing to affect the maritime security of the United States.<o:p></o:p></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div style="mso-element: endnote-list;">
<!--[if !supportEndnotes]--><br clear="all" />
<hr align="left" size="1" width="33%" />
<!--[endif]-->
<br />
<div id="edn1" style="mso-element: endnote;">
<div class="MsoEndnoteText">
<a href="file:///C:/Users/lthom_000/Desktop/OIG%20post.docx#_ednref1" name="_edn1" style="mso-endnote-id: edn1;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "calibri" , sans-serif; font-size: 10.0pt; line-height: 107%;">[1]</span></span><!--[endif]--></span></span></a> Congress.gov.
Public Law 144-278, Dec. 16, 2016. To require the Secretary of Homeland
Security to prepare a comprehensive security assessment of the transportation
security card program, and for other purposes.<span class="MsoHyperlink"><a href="https://www.congress.gov/114/plaws/publ278/PLAW-114publ278.pdf">https://www.congress.gov/114/plaws/publ278/PLAW-114publ278.pdf</a></span><o:p></o:p></div>
<div class="MsoEndnoteText">
<br /></div>
<div class="MsoEndnoteText">
Public Law 114–278<o:p></o:p></div>
<div class="MsoEndnoteText">
114th Congress <o:p></o:p></div>
<div class="MsoEndnoteText">
An Act<o:p></o:p></div>
<div class="MsoEndnoteText">
To require the Secretary of Homeland Security to
prepare a comprehensive security assessment of the transportation security card
program, and for other purposes.<o:p></o:p></div>
<div class="MsoEndnoteText">
Be it enacted by the Senate and House of
Representatives of the United States of America in Congress assembled,<o:p></o:p></div>
<div class="MsoEndnoteText">
SECTION 1. TRANSPORTATION WORKER IDENTIFICATION
CREDENTIAL SECURITY CARD PROGRAM IMPROVEMENTS AND ASSESSMENT.<o:p></o:p></div>
<div class="MsoEndnoteText">
(a) CREDENTIAL IMPROVEMENTS.—<o:p></o:p></div>
<div class="MsoEndnoteText">
(1) IN GENERAL.—Not later than 60 days after the date
of enactment of this Act, the Administrator of the Transportation Security
Administration shall commence actions, consistent with section 70105 of title
46, United States Code, to improve the Transportation Security Administration’s
process for vetting individuals with access to secure areas of vessels and maritime
facilities.<o:p></o:p></div>
<div class="MsoEndnoteText">
(2) REQUIRED ACTIONS.—The actions described under
paragraph (1) shall include—<o:p></o:p></div>
<div class="MsoEndnoteText">
(A) conducting a comprehensive risk analysis of
security threat assessment procedures, including—<o:p></o:p></div>
<div class="MsoEndnoteText">
(i) identifying those procedures that need additional
internal controls; and<o:p></o:p></div>
<div class="MsoEndnoteText">
(ii) identifying best practices for quality assurance
at every stage of the security threat assessment;<o:p></o:p></div>
<div class="MsoEndnoteText">
(B) implementing the additional internal controls and
best practices identified under subparagraph (A);<o:p></o:p></div>
<div class="MsoEndnoteText">
(C) improving fraud detection techniques, such as—<o:p></o:p></div>
<div class="MsoEndnoteText">
(i) by establishing benchmarks and a process for
electronic document validation;<o:p></o:p></div>
<div class="MsoEndnoteText">
(ii) by requiring annual training for Trusted Agents;
and<o:p></o:p></div>
<div class="MsoEndnoteText">
(iii) by reviewing any security threat assessment
related information provided by Trusted Agents and incorporating any new threat
information into updated guidance under subparagraph (D);<o:p></o:p></div>
<div class="MsoEndnoteText">
(D) updating the guidance provided to Trusted Agents
regarding the vetting process and related regulations;<o:p></o:p></div>
<div class="MsoEndnoteText">
(E) finalizing a manual for Trusted Agents and
adjudicators on the vetting process; and<o:p></o:p></div>
<div class="MsoEndnoteText">
(F) establishing quality controls to ensure consistent
procedures to review adjudication decisions and terrorism<o:p></o:p></div>
<div class="MsoEndnoteText">
vetting decisions.<o:p></o:p></div>
<div class="MsoEndnoteText">
(3) REPORT.—Not later than 2 years after the date of
enactment of this Act, the Inspector General of the Department <span style="mso-spacerun: yes;"> </span>of Homeland Security shall submit a report to
Congress that evaluates the implementation of the actions described in
paragraph (1).<o:p></o:p></div>
<div class="MsoEndnoteText">
(b) COMPREHENSIVE SECURITY ASSESSMENT OF THE
TRANSPORTATION SECURITY CARD PROGRAM.—<o:p></o:p></div>
<div class="MsoEndnoteText">
(1) IN GENERAL.—Not later than 60 days after the date
of enactment of this Act, the Secretary of Homeland Security shall commission
an assessment of the effectiveness of the transportation security card program
(referred to in this section as ‘‘Program’’) required under section 70105 of
title 46, United States Code, at enhancing security and reducing security risks
for facilities and vessels regulated under chapter 701 of that title.<o:p></o:p></div>
<div class="MsoEndnoteText">
(2) LOCATION.—The assessment commissioned under
paragraph (1) shall be conducted by a research organization with significant
experience in port or maritime security, such as—<o:p></o:p></div>
<div class="MsoEndnoteText">
(A) a national laboratory;<o:p></o:p></div>
<div class="MsoEndnoteText">
(B) a university-based center within the Science and
Technology Directorate’s centers of excellence network; or<o:p></o:p></div>
<div class="MsoEndnoteText">
(C) a qualified federally-funded research and
development center.<o:p></o:p></div>
<div class="MsoEndnoteText">
(3) CONTENTS.—The assessment commissioned under
paragraph (1) shall—<o:p></o:p></div>
<div class="MsoEndnoteText">
(A) review the credentialing process by determining—<o:p></o:p></div>
<div class="MsoEndnoteText">
(i) the appropriateness of vetting standards;<o:p></o:p></div>
<div class="MsoEndnoteText">
(ii) whether the fee structure adequately reflects the
current costs of vetting;<o:p></o:p></div>
<div class="MsoEndnoteText">
(iii) whether there is unnecessary redundancy or
duplication with other Federal- or State-issued transportation security
credentials; and<o:p></o:p></div>
<div class="MsoEndnoteText">
(iv) the appropriateness of having varied Federal and
State threat assessments and access controls;<o:p></o:p></div>
<div class="MsoEndnoteText">
(B) review the process for renewing applications for
Transportation Worker Identification Credentials,<o:p></o:p></div>
<div class="MsoEndnoteText">
including the number of days it takes to review
application, appeal, and waiver requests for additional information;<o:p></o:p></div>
<div class="MsoEndnoteText">
and<o:p></o:p></div>
<div class="MsoEndnoteText">
(C) review the security value of the Program by—<o:p></o:p></div>
<div class="MsoEndnoteText">
(i) evaluating the extent to which the Program, as
implemented, addresses known or likely security risks in the maritime and port
environments;<o:p></o:p></div>
<div class="MsoEndnoteText">
(ii) evaluating the potential for a <a href="https://www.blogger.com/null" name="_Hlk533768901">non-biometric credential alternative</a>;<o:p></o:p></div>
<div class="MsoEndnoteText">
(iii) <a href="https://www.blogger.com/null" name="_Hlk533768989">identifying the
technology, business process, and operational impacts of the use of the
transportation<o:p></o:p></a></div>
<div class="MsoEndnoteText">
<span style="mso-bookmark: _Hlk533768989;">security card
and transportation security card readers in the maritime and port environments;<o:p></o:p></span></div>
<div class="MsoEndnoteText">
<span style="mso-bookmark: _Hlk533768989;">(iv) assessing
the costs and benefits of the Program, as implemented; and<o:p></o:p></span></div>
<div class="MsoEndnoteText">
<span style="mso-bookmark: _Hlk533768989;">(v) evaluating
the extent to which the Secretary of Homeland Security has addressed the
deficiencies<o:p></o:p></span></div>
<div class="MsoEndnoteText">
<span style="mso-bookmark: _Hlk533768989;">in the Program
identified by the Government Accountability Office and the Inspector General of
the Department of Homeland Security before the date of enactment of this Act.<o:p></o:p></span></div>
<span style="mso-bookmark: _Hlk533768989;"></span>
<br />
<div class="MsoEndnoteText">
<span style="mso-spacerun: yes;"> </span>(4)
DEADLINES.—The assessment commissioned under paragraph (1) shall be completed
not later than 1 year after the date on which the assessment is commissioned.<o:p></o:p></div>
<div class="MsoEndnoteText">
(5) SUBMISSION TO CONGRESS.—Not later than 60 days
after the date that the assessment is completed, the Secretary of Homeland
Security shall submit to the Committee on Commerce, Science, and Transportation
and the Committee on Homeland Security and Governmental Affairs of the Senate
and the Committee on Homeland Security and the Committee on Transportation and
Infrastructure of the House of Representatives the results of the assessment
commissioned under this subsection.<o:p></o:p></div>
<div class="MsoEndnoteText">
(c) CORRECTIVE ACTION PLAN; PROGRAM REFORMS.—If the
assessment commissioned under subsection (b) identifies a deficiency in the
effectiveness of the Program, the Secretary of Homeland Security, not later
than 60 days after the date on which the assessment is completed, shall submit
a corrective action plan to the Committee on Commerce, Science, and
Transportation and the Committee on Homeland Security and Governmental Affairs<o:p></o:p></div>
<div class="MsoEndnoteText">
of the Senate, the Committee on Homeland Security and
the Committee on Transportation and Infrastructure of the House of
Representatives that—<o:p></o:p></div>
<div class="MsoEndnoteText">
(1) responds to findings of the assessment;<o:p></o:p></div>
<div class="MsoEndnoteText">
(2) includes an implementation plan with benchmarks;<o:p></o:p></div>
<div class="MsoEndnoteText">
(3) may include programmatic reforms, revisions to
regulations, or proposals for legislation; and<o:p></o:p></div>
<div class="MsoEndnoteText">
(4) shall be considered in any rulemaking by the
Department of Homeland Security relating to the Program.<o:p></o:p></div>
<div class="MsoEndnoteText">
(d) INSPECTOR GENERAL REVIEW.—If a corrective action
plan is submitted under subsection (c), the Inspector General of the Department
of Homeland Security shall—<o:p></o:p></div>
<div class="MsoEndnoteText">
(1) not later than 120 days after the date of such
submission, review the extent to which such plan implements the<o:p></o:p></div>
<div class="MsoEndnoteText">
requirements under subsection (c); and<o:p></o:p></div>
<div class="MsoEndnoteText">
(2) not later than 18 months after the date of such
submission, and annually thereafter for 3 years, submit a report<o:p></o:p></div>
<div class="MsoEndnoteText">
to the congressional committees set forth in subsection
(c) that describes the progress of the implementation of such plan.<o:p></o:p></div>
<div class="MsoEndnoteText">
Approved December 16, 2016.<o:p></o:p></div>
</div>
<div id="edn2" style="mso-element: endnote;">
<div class="MsoEndnoteText">
<a href="file:///C:/Users/lthom_000/Desktop/OIG%20post.docx#_ednref2" name="_edn2" style="mso-endnote-id: edn2;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "calibri" , sans-serif; font-size: 10.0pt; line-height: 107%;">[2]</span></span><!--[endif]--></span></span></a>
Ibid.<o:p></o:p></div>
</div>
<div id="edn3" style="mso-element: endnote;">
<div class="MsoEndnoteText">
<a href="file:///C:/Users/lthom_000/Desktop/OIG%20post.docx#_ednref3" name="_edn3" style="mso-endnote-id: edn3;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "calibri" , sans-serif; font-size: 10.0pt; line-height: 107%;">[3]</span></span><!--[endif]--></span></span></a>
Ibid.<o:p></o:p></div>
</div>
<div id="edn4" style="mso-element: endnote;">
<div class="MsoEndnoteText">
<a href="file:///C:/Users/lthom_000/Desktop/OIG%20post.docx#_ednref4" name="_edn4" style="mso-endnote-id: edn4;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "calibri" , sans-serif; font-size: 10.0pt; line-height: 107%;">[4]</span></span><!--[endif]--></span></span></a>
Ibid.<o:p></o:p></div>
</div>
<div id="edn5" style="mso-element: endnote;">
<div class="MsoEndnoteText">
<a href="file:///C:/Users/lthom_000/Desktop/OIG%20post.docx#_ednref5" name="_edn5" style="mso-endnote-id: edn5;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "calibri" , sans-serif; font-size: 10.0pt; line-height: 107%;">[5]</span></span><!--[endif]--></span></span></a>
Ibid.<o:p></o:p></div>
</div>
<div id="edn6" style="mso-element: endnote;">
<a href="file:///C:/Users/lthom_000/Desktop/OIG%20post.docx#_ednref7" name="_edn7" title=""><span class="MsoEndnoteReference"><span class="MsoEndnoteReference"><span style="font-family: "calibri" , sans-serif; font-size: 10.0pt; line-height: 107%;">[7]</span></span></span></a>
Ibid.</div>
<div id="edn7" style="mso-element: endnote;">
<div class="MsoEndnoteText">
<o:p></o:p></div>
</div>
<div id="edn8" style="mso-element: endnote;">
<div class="MsoEndnoteText">
<a href="file:///C:/Users/lthom_000/Desktop/OIG%20post.docx#_ednref8" name="_edn8" style="mso-endnote-id: edn8;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "calibri" , sans-serif; font-size: 10.0pt; line-height: 107%;">[8]</span></span><!--[endif]--></span></span></a>
Ibid.<o:p></o:p></div>
</div>
<div id="edn9" style="mso-element: endnote;">
<div class="MsoEndnoteText">
<a href="file:///C:/Users/lthom_000/Desktop/OIG%20post.docx#_ednref9" name="_edn9" style="mso-endnote-id: edn9;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "calibri" , sans-serif; font-size: 10.0pt; line-height: 107%;">[9]</span></span><!--[endif]--></span></span></a>
Ibid.<o:p></o:p></div>
</div>
<div id="edn10" style="mso-element: endnote;">
<div class="MsoEndnoteText">
<a href="file:///C:/Users/lthom_000/Desktop/OIG%20post.docx#_ednref10" name="_edn10" style="mso-endnote-id: edn10;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "calibri" , sans-serif; font-size: 10.0pt; line-height: 107%;">[10]</span></span><!--[endif]--></span></span></a>U.S.
Department of Homeland Security.<span style="mso-spacerun: yes;"> </span>Office
of the Inspector General. 2018.<span style="mso-spacerun: yes;"> </span>https://www.oig.dhs.gov/about<o:p></o:p></div>
</div>
<div id="edn11" style="mso-element: endnote;">
<div class="MsoEndnoteText">
<a href="file:///C:/Users/lthom_000/Desktop/OIG%20post.docx#_ednref11" name="_edn11" style="mso-endnote-id: edn11;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "calibri" , sans-serif; font-size: 10.0pt; line-height: 107%;">[11]</span></span><!--[endif]--></span></span></a> U.S.
Department of Homeland Security. Transportation Security Administration.
Factsheet: TSA by the Numbers. 2019.
https://www.tsa.gov/sites/default/files/resources/tsabythenumbers_factsheet.pdf<o:p></o:p></div>
</div>
<div id="edn12" style="mso-element: endnote;">
<div class="MsoEndnoteText">
<a href="file:///C:/Users/lthom_000/Desktop/OIG%20post.docx#_ednref12" name="_edn12" style="mso-endnote-id: edn12;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "calibri" , sans-serif; font-size: 10.0pt; line-height: 107%;">[12]</span></span><!--[endif]--></span></span></a>
Ibid.<o:p></o:p></div>
</div>
<div id="edn13" style="mso-element: endnote;">
<div class="MsoEndnoteText">
<a href="file:///C:/Users/lthom_000/Desktop/OIG%20post.docx#_ednref13" name="_edn13" style="mso-endnote-id: edn13;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "calibri" , sans-serif; font-size: 10.0pt; line-height: 107%;">[13]</span></span><!--[endif]--></span></span></a> United
States Government Accountability Office. Transportation Security
Administration: Surface<o:p></o:p></div>
<div class="MsoEndnoteText">
Transportation Inspector Activities Should Align More
Closely With Identified Risks. GAO-18-180. December 2017. https://www.gao.gov/assets/690/689031.pdf<o:p></o:p></div>
</div>
<div id="edn14" style="mso-element: endnote;">
<div class="MsoEndnoteText">
<a href="file:///C:/Users/lthom_000/Desktop/OIG%20post.docx#_ednref14" name="_edn14" style="mso-endnote-id: edn14;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "calibri" , sans-serif; font-size: 10.0pt; line-height: 107%;">[14]</span></span><!--[endif]--></span></span></a>
Clark, Charles S. Vacancy Rate for Top Agency Jobs Continues to Set Records.
Government Executive. August 1, 2018. <o:p></o:p></div>
<div class="MsoEndnoteText">
https://www.govexec.com/management/2018/08/vacancy-rate-top-agency-jobs-continues-set-records/150224/<o:p></o:p></div>
</div>
<div id="edn15" style="mso-element: endnote;">
<div class="MsoEndnoteText">
<a href="file:///C:/Users/lthom_000/Desktop/OIG%20post.docx#_ednref15" name="_edn15" style="mso-endnote-id: edn15;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "calibri" , sans-serif; font-size: 10.0pt; line-height: 107%;">[15]</span></span><!--[endif]--></span></span></a>
The White House. White House Internship Program. Presidential Departments.
2018.<span style="mso-spacerun: yes;"> </span>https://www.whitehouse.gov/get-involved/internships/presidential-departments/<o:p></o:p></div>
</div>
<div id="edn16" style="mso-element: endnote;">
<div class="MsoEndnoteText">
<a href="file:///C:/Users/lthom_000/Desktop/OIG%20post.docx#_ednref16" name="_edn16" style="mso-endnote-id: edn16;" title=""><span class="MsoEndnoteReference"><span style="mso-special-character: footnote;"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-family: "calibri" , sans-serif; font-size: 10.0pt; line-height: 107%;">[16]</span></span><!--[endif]--></span></span></a>
Fund, John. Trump Is Running a ‘Home Alone’ Administration. National Review.
March 25, 2018. https://www.nationalreview.com/2018/03/trump-administration-staff-vacancies-leave-career-civil-servants-in-place/<o:p></o:p></div>
</div>
</div>
<br />Laurie Thomashttp://www.blogger.com/profile/16611719448125721800noreply@blogger.com0tag:blogger.com,1999:blog-1555376450970352963.post-89947775863388283972018-08-06T13:02:00.001-07:002018-08-06T13:02:37.553-07:00Latest Developments that will Affect Implementation of the TWIC Reader Final Rule<br />
<div class="MsoNormal">
On August 02, 2018, HR 5729 was signed into law, becoming Public
Law No: 115-230,The <span style="mso-spacerun: yes;"> </span>Transportation
Worker Identification Credential Accountability Act of 2018.<span style="mso-spacerun: yes;"> </span>The law is so brief that it is quoted in its
entirety at the end of this post.<span style="mso-spacerun: yes;"> </span>It
prohibits the Coast Guard from implementing the TWIC Reader Final Rule and proposing
or issuing a notice of proposed rulemaking for any revision to that rule except
to extend its effective date, or for any other rule requiring the use of
biometric readers for biometric transportation security cards. The Coast Guard
may not do any of this before the end of the 60-day period after submission to
Congress of the results of an assessment of the effectiveness of the TWIC
program, required under a 2016 law mandating a comprehensive security
assessment of the program. TSA was supposed to have commenced and completed
this assessment of the TWIC program in 2017, but I can find no evidence on the
relevant congressional committee websites of testimony on the assessment. <o:p></o:p></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
On August 03 the Coast Guard published a post on Maritime
Commons, Latest Developments Regarding the TWIC Reader Final Rule, at <a href="http://mariners.coastguard.dodlive.mil/2018/08/03/8-3-2018-latest-developments-regarding-twic-reader-final-rule/">http://mariners.coastguard.dodlive.mil/2018/08/03/8-3-2018-latest-developments-regarding-twic-reader-final-rule/</a>,
advising about HR 5729.<o:p></o:p></div>
<div class="MsoNormal">
The Maritime Commons post gives some information from <i style="mso-bidi-font-style: normal;">International Liquid Terminals Association
et. al. v. DHS</i>, the industry groups lawsuit against the TWIC reader rule,
that also impacts implementation of the rule: “Additionally, the United States
District Court for the Eastern District of Virginia issued a court order July
24, 2018, delaying the TWIC Reader Final Rule implementation at Certain
Dangerous Cargo transfer and non-transfer facilities until further order of the
Court, in response to a lawsuit brought by industry groups.”<o:p></o:p></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
What this will probably mean for us is that the clock has
been stopped on the TWIC reader final rule – not just for certain classes of
facilities, but for all facilities subject to the rule. Maritime Commons states
in the August 03 post that “The Office of Port and Facility Compliance will
provide additional information regarding the impacts of this law, the current
lawsuit, and the Notice of Proposed Rulemaking in the near future.”<o:p></o:p></div>
<div class="MsoNormal">
______________________________________________________<o:p></o:p></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
Public Law No: 115-230<o:p></o:p></div>
<div class="MsoNormal">
An Act, To restrict the department in which the Coast Guard
is operating from implementing any rule requiring the use of biometric readers
for biometric transportation security cards until after submission to Congress
of the results of an assessment of the effectiveness of the transportation
security card program.<o:p></o:p></div>
<div class="MsoNormal">
Be it enacted by the Senate and House of Representatives of
the United States of America in Congress assembled,<o:p></o:p></div>
<div class="MsoNormal">
SECTION 1. SHORT TITLE.<o:p></o:p></div>
<div class="MsoNormal">
This Act may be cited as the “Transportation Worker
Identification Credential Accountability Act of 2018”.<o:p></o:p></div>
<div class="MsoNormal">
SEC. 2. RESTRICTION ON IMPLEMENTATION OF TRANSPORTATION
WORKER IDENTIFICATION CREDENTIAL BIOMETRIC READER RULE.<o:p></o:p></div>
<div class="MsoNormal">
The department in which the Coast Guard is operating may not
implement the rule entitled “Transportation Worker Identification Credential
(TWIC)–Reader Requirements” (81 Fed. Reg. 57651), and may not propose or issue
a notice of proposed rulemaking for any revision to such rule except to extend
its effective date, or for any other rule requiring the use of biometric
readers for biometric transportation security cards under section 70105(k)(3)
of title 46, United States Code, before the end of the 60-day period beginning
on the date of the submission under paragraph (5) of section 1(b) of Public Law
114–278 (130 Stat. 1411 to 1412) of the results of the assessment required by
that section.<o:p></o:p></div>
<div class="MsoNormal">
SEC. 3. PROGRESS UPDATES.<o:p></o:p></div>
<div class="MsoNormal">
Not later than 30 days after the date of the enactment of
this Act, and every 90 days thereafter until the submission under paragraph (5)
of section 1(b) of Public Law 114–278 (130 Stat. 1411 et seq.) of the results
of the assessment required by that section, the Secretary of Homeland Security
shall report to the Committee on Homeland Security and the Committee on
Transportation and Infrastructure of the House of Representatives and the
Committee on Commerce, Science, and Transportation of the Senate regarding the
implementation of that section.<o:p></o:p></div>
<br />Laurie Thomashttp://www.blogger.com/profile/16611719448125721800noreply@blogger.com0tag:blogger.com,1999:blog-1555376450970352963.post-23309954008350330532018-07-11T06:37:00.000-07:002018-07-11T06:45:19.799-07:00TSA Begins Issuing New TWIC Design<br />
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">From TSA, 07/10/2018: "The
Transportation Security Administration (TSA) began issuing a new, more secure
Transportation Worker Identification Credential (TWIC®) on July 10, 2018.
Incorporating enhanced security features, the new TWIC® design aims to deter
counterfeiting efforts and mitigate the fraudulent use of the credential at
regulated facilities and vessels. Below are some key details about the new
card:<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoListParagraph" style="margin-left: 45.75pt; mso-list: l0 level1 lfo1; text-indent: -27.75pt;">
<!--[if !supportLists]--><span style="font-family: Arial, Helvetica, sans-serif;"><span style="mso-fareast-font-family: Calibri;"><span style="mso-list: Ignore;">•<span style="font-size: 7pt; font-stretch: normal; font-style: normal; font-variant: normal; font-weight: normal; line-height: normal;">
</span></span></span><!--[endif]-->Current TWIC® card holders do not need to
replace a valid TWIC® card with the new TWIC® card design. <o:p></o:p></span></div>
<div class="MsoListParagraph" style="margin-left: 45.75pt; mso-list: l0 level1 lfo1; text-indent: -27.75pt;">
<!--[if !supportLists]--><span style="font-family: Arial, Helvetica, sans-serif;"><span style="mso-fareast-font-family: Calibri;"><span style="mso-list: Ignore;">•<span style="font-size: 7pt; font-stretch: normal; font-style: normal; font-variant: normal; font-weight: normal; line-height: normal;">
</span></span></span><!--[endif]-->Regulated entities that require TWIC® for access
will accept and recognize both the current and new TWIC® designs until the
card’s expiration. <o:p></o:p></span></div>
<div class="MsoListParagraph" style="margin-left: 45.75pt; mso-list: l0 level1 lfo1; text-indent: -27.75pt;">
<!--[if !supportLists]--><span style="font-family: Arial, Helvetica, sans-serif;"><span style="mso-fareast-font-family: Calibri;"><span style="mso-list: Ignore;">•<span style="font-size: 7pt; font-stretch: normal; font-style: normal; font-variant: normal; font-weight: normal; line-height: normal;">
</span></span></span><!--[endif]-->The new card design is compatible with qualified
TWIC® readers.<o:p></o:p></span></div>
<div class="MsoListParagraph" style="margin-left: 45.75pt; mso-list: l0 level1 lfo1; text-indent: -27.75pt;">
<!--[if !supportLists]--><span style="font-family: Arial, Helvetica, sans-serif;"><span style="mso-fareast-font-family: Calibri;"><span style="mso-list: Ignore;">•<span style="font-size: 7pt; font-stretch: normal; font-style: normal; font-variant: normal; font-weight: normal; line-height: normal;">
</span></span></span><!--[endif]-->To deter alteration of the card’s expiration
date, the new card includes a color-coded expiration date box that will update
on an annual basis.<o:p></o:p></span></div>
<div class="MsoListParagraph" style="margin-left: 45.75pt; mso-list: l0 level1 lfo1; text-indent: -27.75pt;">
<!--[if !supportLists]--><span style="font-family: Arial, Helvetica, sans-serif;"><span style="mso-fareast-font-family: Calibri;"><span style="mso-list: Ignore;">•<span style="font-size: 7pt; font-stretch: normal; font-style: normal; font-variant: normal; font-weight: normal; line-height: normal;">
</span></span></span><!--[endif]-->The fee for the newly re-designed TWIC® card
remains unchanged ($125.25) and the credential is valid for five years."<o:p></o:p></span><br />
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span>
<span style="font-family: Arial, Helvetica, sans-serif;">A <span style="font-size: 11pt; text-indent: -27.75pt;">“TWIC Authentication Guide” document focused on the overt security features of
the new TWIC® card design has been cleared for public
release. </span></span><br />
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span>
<span style="font-family: Arial, Helvetica, sans-serif;">Please note, TSA did not <span style="text-indent: -27.75pt;"><span style="font-size: 11pt;">approve, disapprove, or endorse this </span><span style="font-size: 14.6667px;">blog post.</span><span style="font-size: 11pt;"> </span></span></span></div>
<br />Laurie Thomashttp://www.blogger.com/profile/16611719448125721800noreply@blogger.com0tag:blogger.com,1999:blog-1555376450970352963.post-9914595209660758512018-06-29T06:45:00.002-07:002018-06-29T06:45:41.072-07:00<h2 style="background-attachment: initial; background-clip: initial; background-image: initial; background-origin: initial; background-position: 0px 0px; background-repeat: initial; background-size: initial; border: 0px; box-sizing: border-box; color: rgba(0, 0, 0, 0.9); counter-reset: list-1 0 list-2 0 list-3 0 list-4 0 list-5 0 list-6 0 list-7 0 list-8 0 list-9 0; cursor: text; font-family: -apple-system, system-ui, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", "Fira Sans", Ubuntu, Oxygen, "Oxygen Sans", Cantarell, "Droid Sans", "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Emoji", "Segoe UI Symbol", "Lucida Grande", Helvetica, Arial, sans-serif; font-size: 24px; line-height: 32px; margin: 0px 0px 2.8rem; outline: 0px; padding: 0px; vertical-align: baseline; white-space: pre-wrap;">
USCG Maritime Commons Announces New Form for Documenting Facilities Inspection</h2>
<div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">In the 06/28/2018 posting in Maritime Commons, the Coast
Guard Blog for Maritime Professionals, the Coast Guard announced a change in
documentation for facility inspections. The CG-835 form is being replaced by
the CG-835F. There are no major differences between the two forms but
facilities may notice the following:<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoListParagraphCxSpFirst" style="mso-list: l0 level1 lfo1; text-indent: -.25in;">
<!--[if !supportLists]--><span style="font-family: Arial, Helvetica, sans-serif;"><span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;">1.<span style="font-size: 7pt; font-stretch: normal; font-style: normal; font-variant: normal; font-weight: normal; line-height: normal;">
</span></span></span><!--[endif]-->The 835 is a combined vessel and facility
inspection form. The 835F is specifically designed for facilities inspection,
and contains a space for the MISLE activity number. MISLE is the Coast Guard’s Marine
Information for Safety and Law Enforcement data information system. For more
information on MISLE, see https://www.dhs.gov/publication/dhsuscgpia-008-marine-information-safety-and-law-enforcement-misle.<o:p></o:p></span></div>
<div class="MsoListParagraphCxSpMiddle" style="mso-list: l0 level1 lfo1; text-indent: -.25in;">
<!--[if !supportLists]--><span style="font-family: Arial, Helvetica, sans-serif;"><span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;">2.<span style="font-size: 7pt; font-stretch: normal; font-style: normal; font-variant: normal; font-weight: normal; line-height: normal;">
</span></span></span><!--[endif]-->Directions are different on the two forms. The
835 directs, “You must inform the inspecting officer when the following have
been corrected.” The 835F emphasizes compliance and states, “Contact the
inspecting officer when the following item(s) have been corrected.”<o:p></o:p></span></div>
<div class="MsoListParagraphCxSpMiddle" style="mso-list: l0 level1 lfo1; text-indent: -.25in;">
<!--[if !supportLists]--><span style="font-family: Arial, Helvetica, sans-serif;"><span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;">3.<span style="font-size: 7pt; font-stretch: normal; font-style: normal; font-variant: normal; font-weight: normal; line-height: normal;">
</span></span></span><!--[endif]-->Size matters: the 835 is a smaller form, harder
to file and easier to misplace. The 835F is an 8.5 x 11 form which can be
3-hole punched for easier filing in paper copy.<o:p></o:p></span></div>
<div class="MsoListParagraphCxSpLast" style="mso-list: l0 level1 lfo1; text-indent: -.25in;">
<!--[if !supportLists]--><span style="font-family: Arial, Helvetica, sans-serif;"><span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;">4.<span style="font-size: 7pt; font-stretch: normal; font-style: normal; font-variant: normal; font-weight: normal; line-height: normal;">
</span></span></span><!--[endif]-->The 835F has a second page that details the rights
of appeal for facilities who want to request consideration.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">The Maritime Commons post states that “Regulated facilities
should note that Coast Guard facility inspectors may begin using the CG-835F to
document facility inspections, but in some instances may continue to use the
CG-835 during this transition.”<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">Maritime Commons, the Coast Guard Blog for Maritime
Professionals, is an excellent source of information concerning MTSA issues,
facility compliance, and general Coast Guard news. You can subscribe to
Maritime Commons at <a href="http://mariners.coastguard.dodlive.mil/">http://mariners.coastguard.dodlive.mil/</a>.<span style="mso-spacerun: yes;"> </span></span><o:p></o:p></div>
</div>
Laurie Thomashttp://www.blogger.com/profile/16611719448125721800noreply@blogger.com0tag:blogger.com,1999:blog-1555376450970352963.post-78857838246779882362017-07-12T19:33:00.000-07:002017-07-12T19:33:46.685-07:00Draft Navigation and Vessel Inspection Circular No. 05-17, Guidelines for Addressing Cyber Risks at Maritime Transportation Security Act (MTSA) Facilities<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: "arial" , "helvetica" , sans-serif;">In the July 12, 2017 Federal
Register, the Coast Guard posted the notice of the publication of Draft
Navigation and Vessel Inspection Circular (NVIC) No. 05-17, Guidelines for Addressing
Cyber Risks at Maritime Transportation Security Act (MTSA) Facilities. The NVIC is available at <a href="https://www.regulations.gov/document?D=USCG-2016-1084-0002">https://www.regulations.gov/document?D=USCG-2016-1084-0002</a>.
Comments must be submitted to </span><span style="font-family: arial, helvetica, sans-serif;">the online docket via http://www.regulations.gov, or reach the Docket
Management Facility, on or </span><span style="font-family: arial, helvetica, sans-serif;">before September 11, 2017.</span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;">Facility Security Officers (FSOs) are advised that this is a draft NVIC, posted for
review, to allow industry an opportunity to give feedback and commentary which
the Coast Guard will evaluate and incorporate in the final version of the NVIC.
This is a richly detailed performance standard on implementation of security
measures to ward off the worst threat looming over us.<o:p></o:p></span><br />
<span style="font-family: "arial" , "helvetica" , sans-serif;"><br /></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: "arial" , "helvetica" , sans-serif;">It is possible that Facility Security Plan sections 2, 3, 4, 5, 6, 8, 9,
10, 11, 12, 13, and 16 as well as the Facility Security Assessment may be
affected by this NVIC. This is not a lengthy document (37 pages) so FSOs are
encouraged to read it in its entirety. The amount of detail was difficult to
summarize, especially Enclosure 2, and only the organization and main points
are described below.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: "arial" , "helvetica" , sans-serif;">__________________________________________________________<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: "arial" , "helvetica" , sans-serif;">SUMMARY OF THE NVIC (largely taken from the text. My words are in<i> italics</i>) The NVIC has two enclosures.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: "arial" , "helvetica" , sans-serif;">(1) Cyber Security and MTSA<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: "arial" , "helvetica" , sans-serif;">(2) Cyber Governance and Cyber Risk Management Program Implementation
Guidance<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: "arial" , "helvetica" , sans-serif;">Purpose: MTSA-regulated
facilities are instructed to analyze vulnerabilities with computer systems and
networks in their Facility Security Assessments. This NVIC will assist FSOs in
completing this requirement. Additionally, this NVIC provides guidance and
recommended practices for MTSA regulated facilities to address cyber related
vulnerabilities. Until specific cyber risk management regulations are
promulgated, facility operators may use this document as guidance to develop
and implement measures and activities for effective self governance of cyber vulnerabilities.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: "arial" , "helvetica" , sans-serif;">Background: The Coast Guard currently has the regulatory authority to
instruct facilities and Outer Continental Shelf (OCS) facilities regulated
under MTSA to analyze computer systems and networks for potential vulnerabilities
within their required FSA and, if necessary, FSP.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: "arial" , "helvetica" , sans-serif;">DISCLAIMER. This guidance is not a substitute for applicable legal
requirements, nor is it itself </span><span style="font-family: "arial" , "helvetica" , sans-serif;">a rule. It is not intended to nor does it impose legally binding
requirements on any party. It </span><span style="font-family: "arial" , "helvetica" , sans-serif;">represents the Coast Guard’s current thinking on this topic and may
assist industry, mariners, the </span><span style="font-family: "arial" , "helvetica" , sans-serif;">general public, and the Coast Guard, as well as other federal and state
regulators, in applying </span><span style="font-family: "arial" , "helvetica" , sans-serif;">statutory and regulatory requirements.</span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<b><span style="font-family: "arial" , "helvetica" , sans-serif;">Enc. 1 Cyber Security and
MTSA: 33 CFR Parts 105 and 106.<o:p></o:p></span></b></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: "arial" , "helvetica" , sans-serif;">The Coast Guard interprets (threats) to specifically include threats to
computer systems and attacks in the electronic (cyber) domain.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: "arial" , "helvetica" , sans-serif;">In this draft document, the Coast Guard is laying out its
interpretation of regulatory provisions in parts 105 and 106 as applicable to
electronic and cybersecurity systems. This enclosure discusses the specific
regulatory provisions that instruct owners/operators of a Maritime
Transportation Security Act (MTSA) regulated facility to address cyber/computer
system security in the Facility Security Assessment (FSA) and, if applicable,
provide guidance within their FSPs to address any vulnerabilities identified in </span><span style="font-family: "arial" , "helvetica" , sans-serif;">the Facility Security Assessment (FSA). This document intends to assist
the owner/operator in identifying cyber systems that are related to MTSA
regulatory functions, or whose failure or exploitation could cause or
contribute to a Transportation Security Incident. If there are electronic or
cybersecurity-related vulnerabilities identified in an FSA, an owner/operator
may choose to provide this information in a </span><span style="font-family: "arial" , "helvetica" , sans-serif;">variety of formats, such as a stand-alone cyber annex to their FSP, or
by incorporating </span><span style="font-family: "arial" , "helvetica" , sans-serif;">cybersecurity procedures alongside the physical security measures of
their FSP.</span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: "arial" , "helvetica" , sans-serif;"><i>For facilities with strong cyber
programs - </i>In many cases, companies have established cybersecurity and risk
management programs that provide for strong cyber defense. For those
situations, the owner/operator may demonstrate that those policies meet or
exceed the requirements of 33 CFR parts 105 and 106. Owners/operators that
already employ a comprehensive cybersecurity plan for their </span><span style="font-family: "arial" , "helvetica" , sans-serif;">organization, or who wish to apply a standard security program that
incorporates </span><span style="font-family: "arial" , "helvetica" , sans-serif;">cybersecurity to multiple facilities, may wish to submit a security
plan under the </span><span style="font-family: "arial" , "helvetica" , sans-serif;">Alternative Security Program, 33 CFR 101.120.</span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: "arial" , "helvetica" , sans-serif;"><i>How detailed does the FSA or FSP
need to be?</i> Owners/operators do not need to indicate specific or technical
controls, but should provide general documentation on how they are addressing
their cyber risks.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<i><span style="font-family: "arial" , "helvetica" , sans-serif;">Cyber components for 33 CFR:<o:p></o:p></span></i></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: "arial" , "helvetica" , sans-serif;">Recommended Cyber Analysis as part of the FSA: <i>The
NVIC gives information on how to provide the cyber component for 105.305
(d)(2)(v).<o:p></o:p></i></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: "arial" , "helvetica" , sans-serif;"><i>Under</i> “<i>Recommendation to Address Identified Cyber Vulnerabilities (as
applicable)” the NVIC gives</i> <i> general, recommended guidance on how to
mitigate cyber vulnerabilities determined during the FSA by regulation/FSP
section. I can see most facilities describing cyber measures for most of the
sections, which will require FSP amendments. There is guidance here on what the
Coast Guard wants to see in the FSP sections as relating to cyber. <o:p></o:p></i></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: "arial" , "helvetica" , sans-serif;"><b>Enc. 2 Cyber Governance and
Cyber Risk Management Program Implementation Guidance.</b> <i>The Coast Guard details how the NIST Cybersecurity Framework (CSF) can
be implemented in the maritime environment.</i> Sections 1 – 4 of this
enclosure utilize the NIST CSF as the recommended foundation for development of
a cyber risk management program. Facility owner/operators should consider these
guidelines in conjunction with their own risk management policies to help
ensure they account for cyber risks. <i>The
four sections of this enclosure are:<o:p></o:p></i></span></div>
<div class="MsoListParagraph" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-add-space: auto; mso-list: l0 level1 lfo1; text-indent: -.25in;">
<!--[if !supportLists]--><span style="font-family: "arial" , "helvetica" , sans-serif;"><i>1.<span style="font-size: 7pt; font-stretch: normal; font-style: normal; font-variant-numeric: normal; line-height: normal;"> </span></i><!--[endif]--><i>Establishing Cyber Risk Management: Forming
a Cyber Risk Management<o:p></o:p></i></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<i><span style="font-family: "arial" , "helvetica" , sans-serif;"> Team
(CRMT), Defining Cyber Risk Management Policy, and Establishing a<o:p></o:p></span></i></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<i><span style="font-family: "arial" , "helvetica" , sans-serif;"> Cyber Risk Management Program<o:p></o:p></span></i></div>
<div class="MsoListParagraphCxSpFirst" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-add-space: auto; mso-list: l0 level1 lfo1; text-indent: -.25in;">
<!--[if !supportLists]--><span style="font-family: "arial" , "helvetica" , sans-serif;"><i>2.<span style="font-size: 7pt; font-stretch: normal; font-style: normal; font-variant-numeric: normal; line-height: normal;"> </span></i><!--[endif]--><i>Enterprise-Wide Inventory and Analysis<o:p></o:p></i></span></div>
<div class="MsoListParagraphCxSpMiddle" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-add-space: auto; mso-list: l0 level1 lfo1; text-indent: -.25in;">
<!--[if !supportLists]--><span style="font-family: "arial" , "helvetica" , sans-serif;"><i>3.<span style="font-size: 7pt; font-stretch: normal; font-style: normal; font-variant-numeric: normal; line-height: normal;"> </span></i><!--[endif]--><i>Consequence Analysis, Vulnerability
Analysis, and Prioritization<o:p></o:p></i></span></div>
<div class="MsoListParagraphCxSpLast" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-add-space: auto; mso-list: l0 level1 lfo1; text-indent: -.25in;">
<!--[if !supportLists]--><span style="font-family: "arial" , "helvetica" , sans-serif;"><i>4.<span style="font-size: 7pt; font-stretch: normal; font-style: normal; font-variant-numeric: normal; line-height: normal;"> </span></i><!--[endif]--><i>Protect, Detect, Respond, and Recover.<o:p></o:p></i></span></div>
<div class="MsoListParagraphCxSpLast" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in; mso-add-space: auto; mso-list: l0 level1 lfo1; text-indent: -.25in;">
<span style="font-family: "arial" , "helvetica" , sans-serif;"><i><br /></i></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<i><span style="font-family: "arial" , "helvetica" , sans-serif;">These are the nuts and bolts of
the cyber security measures, so to speak: how the USCG suggests that the NIST Framework
can be translated over into the MTS. Each section is detailed and written in
plain understandable English, unlike many cyber publications. Throughout these
sections, where appropriate, the NVIC gives examples of suggested procedures to
follow. There’s a lot of what-to-do and why-we-do-it. The 4.1 Protect Section
is particularly rich with bulleted lists. <o:p></o:p></span></i></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<br />
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<i><span style="font-family: "arial" , "helvetica" , sans-serif;">Appendix A contains tables and metrics
- methods for measuring and scoring cyber vulnerability. Table 1 is a Consequence
Evaluation Guide for vulnerability assessments, linking how bad it is to a
number. Table 2 is a Consequence Score Action (document/consider/mitigate as
relates to cyber, using the score from Table 1) matrix, for scoring scenarios
for Facility Security Assessments. Table 3 is a Connective Vector Assessment
and will assist operators in determining which systems perform or are related
to these critical security and safety functions by examining the purposes and
connections of each system. “Yes” responses from Table 3 are then evaluated
using Table 4, the Cyber Infrastructure Vulnerability Assessment. Each system
that receives a “no” in Table 4 should be evaluated through Table 5, the Vulnerability
Severity Assessment, where it will receive a vulnerability score. Systems with
the highest TOTAL score (at the bottom of Table 5) should be considered the
most vulnerable.</span><o:p></o:p></i></div>
Laurie Thomashttp://www.blogger.com/profile/16611719448125721800noreply@blogger.com0tag:blogger.com,1999:blog-1555376450970352963.post-74166281494316326332017-06-02T06:17:00.000-07:002017-06-02T06:17:34.343-07:00New Information from MARAD About Maritime Security Communications with Industry<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">From the April meeting of the National Maritime Security
Advisory Committee, new information from MARAD about maritime security
communications with industry. Information about the new program can be found
at <a href="https://www.marad.dot.gov/environment-and-safety/office-of-security/msci/">https://www.marad.dot.gov/environment-and-safety/office-of-security/msci/</a><o:p></o:p></span></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">From this website: The U.S. Maritime Administration has
established a new interagency approach to communicating with U.S. maritime
industry stakeholders regarding identified maritime security threats. The new
system, U.S. Maritime Advisory System, replaces Special Warnings to Mariners
(previously generated by the U.S. Department of State’s Office of
Transportation Policy), MARAD Advisories (previously generated by the
Department of Transportation’s Maritime Administration), and global maritime
security focused Marine Safety Information Bulletins (previously generated by
the Department of Homeland Security’s U.S. Coast Guard), to more effectively
and efficiently communicate with U.S. maritime industry stakeholders and U.S.
mariners regarding identified threats in the maritime domain.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">Two new instruments will be issued through the System, U.S.
Maritime Alerts and U.S. Maritime Advisories. The <b>U.S. Maritime Alert</b> is a new tool that has been developed to
expeditiously provide basic information (location, incident type, and
date/time) on reported maritime security threats to U.S. maritime industry
interests. In some situations, a U.S.
Maritime Alert may be issued to refute unsubstantiated claims. U.S. Maritime
Alerts do not contain policy or recommendations for specific courses of action
(this type of information is reserved for U.S. Maritime Advisories). A <b>U.S. Maritime</b> <b>Advisory</b> may follow the issuance of a U.S. Maritime Alert and is
intended to provide more detailed information, when appropriate, through a
“whole-of-government” response to an identified maritime threat.</span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"> Both
instruments will normally be transmitted by the National
Geospatial-Intelligence Agency, will be emailed to U.S. maritime industry
stakeholders, and will be posted to this web portal to inform mariners of
identified maritime security threats. Vessel Masters, Company Security Officers,
ship operators, U.S. mariners, maritime industry associations, U.S. maritime
unions and professional associations, and U.S. mariner related non-governmental
organizations are the intended recipients of these messages. Maritime industry
stakeholders wishing to be added to the email distribution list for U.S.
Maritime Alerts and U.S. Maritime Advisories should email their request to <a href="mailto:MaradSecurity@dot.gov">MaradSecurity@dot.gov</a>.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">______________________________________________________________________</span></div>
<div class="MsoNormal">
<br /></div>
<br />
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">Please note: This blog always quotes heavily from the
sources identified in the opening paragraph. I acknowledge that I should
probably be using quotation marks and block indentation. Readers should assume
that text is from the source and not original with the blog author unless
otherwise stated.</span><o:p></o:p></div>
Laurie Thomashttp://www.blogger.com/profile/16611719448125721800noreply@blogger.com0tag:blogger.com,1999:blog-1555376450970352963.post-72242798371861067502017-05-02T10:36:00.000-07:002017-05-02T10:36:24.135-07:00Draft NVIC on Cybersecurity Coming Soon<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">During the April 25-26 2017 meeting of the National Maritime
Security Advisory Committee (NMSAC), the Committee was given a regulatory
update by U.S. Coast Guard personnel. During this update, the Committee was
advised that the draft Navigation and Vessel Inspection Circular (NVIC) on
cybersecurity would soon be published. Below are some thoughts on this NVIC and
what the Coast Guard has said about the need for a proactive approach to
cybersecurity.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">During the Maritime Cyber Security Standards Public Meeting
on January 15, 2015, discussing the need for voluntary cyber standards, Rear
Admiral Paul Thomas, Assistant Commandant for Prevention Policy, stated, “The
Coast Guard just recently conducted a study about the cost burden to industry
of all the regulations that we have published since 1973. We found that 88% of
the entire cost burdens of all regulations, over all those years, were due to
two regulations, OPA 90 and MTSA. Both of these regulations followed
predictable disasters. The lesson
learned should be that we should not wait for an incident to occur that will
make us move forward on reactive, more expensive, regulations; we need to be
proactive in approaching this. We are here to have a discussion with industry
so we can develop a standard together, one that works and is reasonable in
terms of the cost benefit. If we wait
until an incident occurs, that opportunity goes away.” (as quoted in Cyber Risk
Management, by LCDR Josh Rose & LT Josie Long, http://aapa.files.cms-plus.com/SeminarPresentations/2015Seminars/2015Cybersecurity/Rose%20USCG%20CYBER.pdf)<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">In the Rose/Long AAPA presentation, there was a slide concerning the
cybersecurity NVIC. Bullet points about this NVIC content include:<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">• How do we incorporate cyber into risk assessments?<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">•What tools are available for industry to use for risk assessments?<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">•MTS standard terms (definitions)<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">•What are examples of industrial control systems in the maritime
environment (what is the scope of NVIC)?<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">I think one issue that may be addressed in the NVIC is the link
between the NIST framework and the Facility Security Plan (FSP) – incorporation of cyber into facility
security assessments; guidance for construction of a possible voluntary cyber
annex or new FSP section that directly addresses the Framework elements of identify,
protect, detect, respond, and recover; guidance for inspectors who encounter
these new sections or annexes in annual compliance inspections or during
incident post-review. (We'll see how well my crystal ball is functioning.)<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<br />
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">This will be a draft NVIC, probably titled “For review and
comment only. Not to be used as final guidance.” As a draft NVIC, it will
probably be numbered 17-XX, rather than receiving two numbers as the terminal
designation. In the Federal Register notice of its publication, there will
probably be a section titled Public Participation and Request for Comments. In this section, there will probably be sub-sections
explaining how to submit comments ad how to view comments and documents. (Lots
of probably’s!)</span><o:p></o:p></div>
Laurie Thomashttp://www.blogger.com/profile/16611719448125721800noreply@blogger.com0tag:blogger.com,1999:blog-1555376450970352963.post-48397480129624161652017-04-03T06:39:00.000-07:002017-04-03T06:39:39.304-07:00Coast Guard Maritime Commons Clarifies CDC and TWIC Reader Rule<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;">There has been a lot of discussion about facilities who are
not in Risk Group A but are concerned that they might be included because they “handle
CDC” by truck or railcar away from the MTSA nexus. The TWIC reader final rule
seems to indicate that these facilities will be included in the rule (p.
57681), although the rule also states that the facility may “define its MTSA footprint in such a way as
to exclude that area.” It is presumed that this would require a Facility
Security Plan (FSP) amendment. <o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;">On March 31, 2017, on Coast Guard Maritime Commons, CG-FAC used the
blog to push out important information to industry, clarifying the USCG stance
on facilities that handle CDC. The blog states that facilities should look to
an older Policy Advisory Council decision, 20-04, for guidance on who is and
who is not subject to 33 CFR 105.295 and thus included in Risk Group A. I was
using Chrome to access Maritime Commons and the link to Homeport was not
successful. For other users who also have trouble linking to Homeport, the text of
the PAC is included below in its entirety. Scenarios D and E refer directly to
facilities who handle their CDC by modes other than maritime.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;">To get to this PAC on Homeport, go to <a href="http://homeport.uscg.mil/">http://homeport.uscg.mil</a> then MTSA>MTSA/ISPS Policy Advisory
Council FAQs>20-04 Certain Dangerous Cargo Facilities.pdf<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;">MTSA/ISPS POLICY ADVISORY COUNCIL<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;">May 6, 2004<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;">Issue/Discussion/Decision<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;">Certain Dangerous Cargo Facilities<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;">20-04<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;">FINAL<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;">Issue: What is a CDC facility?<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;">Discussion: Certain Dangerous Cargoes (CDC’s) are defined in
33 CFR 160.204, and the</span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;">preamble to the Final Rule states that facilities that
handle such CDC’s are considered CDC</span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;">Facilities. The Final Rule preamble also notes the Coast
Guard disagrees “that 105.295 should only apply when CDC is actually present on a facility,
because the measures required by the section must be taken in advance so that they can be
implemented when CDC is present.” The Final Rule preamble does not define what the word handles
means, and the purpose of this paper is to decide how to interpret this term.</span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;">Decision: In order for a facility to be classified as a CDC
Facility, a vessel-to-facility<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;">interface must occur, or be capable of occurring, and
involve the transfer of CDC’s in bulk.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;">Facilities designated as CDC facilities would need to comply
with the regulations contained in 33 CFR 105.295. A facility that is required to complete a
Security Plan but that is not designated as a CDC Facility must develop security procedures for the
safeguarding of the CDC while it is present on the facility. The following
scenarios are examples of how this might be accomplished:</span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;">Scenario A: Facilities that receive vessels and engage in
vessel-to-facility interfaces that<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;">involves the transfer of bulk Certain Dangerous Cargoes from
the vessels that they receive.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;">Scenario A Decision: Facilities would be designated as
Certain Dangerous Cargo (CDC)<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;">Facilities and would be required to comply with 33 CFR
105.295.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;">Scenario B: Facilities that receive vessels and engage in
vessel-to-facility interfaces that<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;">involves the transfer of packaged Certain Dangerous Cargoes
from the vessels that they receive.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;">Scenario B Decision: Facilities would not be required to
comply with 33 CFR 105.295. The<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;">Facility Security Plan for these facilities must address the
fact that they handle such cargoes and the provisions that the facilities have to secure such
cargoes. Scenario C: Facilities that receive vessels that carry CDC’s in bulk
but the transfer of CDC’s does not occur between the vessels and the facility.</span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;">Scenario C Decision: Facilities would not be required to
comply with 33 CFR 105.295. Under 33 CFR 105. 245(b), prior to the arrival of a vessel to the
facility, the Facility Security Officer and the Vessel Security Officer, or their designated
representatives, would be required to coordinate security needs and agree upon the contents of a
DoS. The vessel and facility representatives would then need to sign and implement this
DoS. As part of the Security that the two agree upon, provisions should be implemented to
safeguard the CDC onboard the vessel.</span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;">Scenario D: Facilities, already subject to 33 CFR Part 105,
receiving Certain Dangerous<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;">Cargoes from entities other than vessels, such as rail cars
and tanker trucks.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;">Scenario D Decision: Facilities would not be required to
comply with 33 CFR 105.295. The<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;">Facility Security Plan for these facilities must address the
fact that they handle such cargoes and the provisions that the facilities have to secure such
cargoes. At a minimum, these facilities would need to designate the areas where CDC’s are present as
restricted areas.</span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;">Scenario E: Facilities, already subject to 33 CFR Part 105,
through which train cars travel<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;">carrying CDC’s. These CDC’s are not received at the
facility, but the train cars might be present for extended periods of time.</span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;">Scenario E Decision: Facilities would not be required to
comply with 33 CFR 105.295. The<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Times, Times New Roman, serif;">facility should be aware of the movement of such cargoes and
have included this in their Facility Security Plans. At a minimum, the facility should
incorporate the checking of railcars duringsecurity rounds on the facility.</span></div>
<div class="MsoNormal">
<o:p></o:p></div>
Laurie Thomashttp://www.blogger.com/profile/16611719448125721800noreply@blogger.com0tag:blogger.com,1999:blog-1555376450970352963.post-48788348523296906852017-03-31T06:25:00.001-07:002017-03-31T06:25:16.554-07:00Sen John Thune (R-S.D.) introduces S.763, the Surface Transportation and Maritime Security Act.<div class="MsoNormal" style="background: white; line-height: normal; margin-bottom: 7.5pt;">
<span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">On March 30, 2017, Sen John Thune (R-S.D.) introduced S.763,
the Surface Transportation and Maritime Security Act. Sen. Thune is Chairman of the Senate Committee
on Commerce, Science, and Transportation. He’s been in the Senate since 2005
and has served in powerful positions within that body. From Sen. Thune’s
website, at <a href="https://www.thune.senate.gov/public/index.cfm/press-releases?ID=065CC562-BCB2-49FD-82EA-6CE3285E7947">https://www.thune.senate.gov/public/index.cfm/press-releases?ID=065CC562-BCB2-49FD-82EA-6CE3285E7947</a>:<o:p></o:p></span></div>
<div class="MsoNormal" style="background: white; line-height: normal; margin-bottom: 7.5pt;">
<span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">U.S. Sen. John Thune (R-S.D.), chairman of the Senate
Committee on Science, Commerce, and Transportation, joined Sens. Bill Nelson
(D-Fla.), Deb Fischer (R-Neb.), and Cory Booker (D-N.J.) in reintroducing <a href="https://www.commerce.senate.gov/public/_cache/files/cfbf58c6-0fab-4b75-bc85-80870284543f/1612A53B8ACBE938424044272199CF2B.s.-763-surface-and-maritime-transportation-security-act-as-introduced.pdf"><span style="color: windowtext; text-decoration: none; text-underline: none;">S. 763</span></a>,
the Surface Transportation and Maritime Security Act. The legislation, which is
substantially similar to the bill introduced late last Congress, would address
deficiencies in the Transportation Security Administration’s (TSA) efforts to
protect rail, transit, highway, and maritime passenger and freight
transportation.<br />
<br />
“To keep Americans safe, Congress must continually focus attention on areas of
neglect and potential weakness to keep them from becoming targets for
terrorism,” said Thune. “The Commerce Committee will soon vote on these important
reforms for the TSA.”<o:p></o:p></span></div>
<div class="MsoNormal" style="background: white; line-height: normal; margin-bottom: 7.5pt;">
<span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">The legislation would address concerns, raised by
independent government watchdog agencies, that TSA is not adequately positioned
to identify security risks across different modes of transportation or
effectively support federal, state, local and private providers of
transportation security. TSA has previously said in testimony to Congress that
it uses only three percent of its budget on surface transportation security.<br />
<br />
<b>Highlights of the Surface Transportation and Maritime Security Act:</b><br />
<br />
<b><u>Enhances Risk-Based Security Planning</u></b><o:p></o:p></span></div>
<ul type="disc">
<li class="MsoNormal" style="background: white; line-height: normal; mso-list: l3 level1 lfo1; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto; tab-stops: list .5in;"><span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">Requires the TSA administrator
to conduct a risk analysis and implement a risk-based security model for
surface transportation facilities.<o:p></o:p></span></li>
<li class="MsoNormal" style="background: white; line-height: normal; mso-list: l3 level1 lfo1; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto; tab-stops: list .5in;"><span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">Mandates risk-based budgeting
for surface transportation security focusing resources on current threats
with annual reviews of program effectiveness.<o:p></o:p></span></li>
</ul>
<div class="MsoNormal" style="background: white; line-height: normal; margin-bottom: 7.5pt;">
<span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";"><br />
<b><u>Canine Explosive Detection Teams for Surface Transportation</u></b><o:p></o:p></span></div>
<ul type="disc">
<li class="MsoNormal" style="background: white; line-height: normal; mso-list: l2 level1 lfo2; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto; tab-stops: list .5in;"><span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">Authorizes as many as 70
additional canine teams to work in surface transportation security as soon
as possible.<o:p></o:p></span></li>
<li class="MsoNormal" style="background: white; line-height: normal; mso-list: l2 level1 lfo2; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto; tab-stops: list .5in;"><span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">Requires a review of the
number, location, and utilization of canine teams in surface
transportation security to ensure effective use.<o:p></o:p></span></li>
<li class="MsoNormal" style="background: white; line-height: normal; mso-list: l2 level1 lfo2; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto; tab-stops: list .5in;"><span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">Following this review and the
implementation of recommendations, TSA may then raise the total number of
canine teams to 200 or higher as identified in TSA’s risk-based analysis.</span><b><span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";"> </span></b></li>
</ul>
<div class="MsoNormal" style="background: white; line-height: normal; margin-bottom: 7.5pt;">
<b><u><span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">Increases Transparency</span></u></b><span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";"><o:p></o:p></span></div>
<ul type="disc">
<li class="MsoNormal" style="background: white; line-height: normal; mso-list: l1 level1 lfo3; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto; tab-stops: list .5in;"><span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">Mirroring the advisory
committee for aviation established by the Aviation Security Stakeholder
Participation Act of 2014, establishes a Surface Transportation Advisory
Committee to provide stakeholders and the public with the opportunity to
coordinate with the agency and comment on policy and pending
regulations. <o:p></o:p></span></li>
<li class="MsoNormal" style="background: white; line-height: normal; mso-list: l1 level1 lfo3; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto; tab-stops: list .5in;"><span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">Requires that TSA budget
submissions clearly indicate which resources will be used for surface
transportation security and which will be dedicated to aviation.<o:p></o:p></span></li>
<li class="MsoNormal" style="background: white; line-height: normal; mso-list: l1 level1 lfo3; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto; tab-stops: list .5in;"><span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">Directs TSA to regularly update
Congress on the status of long overdue surface transportation rulemakings.<o:p></o:p></span></li>
</ul>
<div class="MsoNormal" style="background: white; line-height: normal; margin-bottom: 7.5pt;">
<b><u><span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";"><br />
Enhances Passenger Rail Security</span></u></b><span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";"><o:p></o:p></span></div>
<ul type="disc">
<li class="MsoNormal" style="background: white; line-height: normal; mso-list: l0 level1 lfo4; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto; tab-stops: list .5in;"><span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">Authorizes the use of
computerized vetting systems for passenger rail at the request of Amtrak
police and the Amtrak Board of Directors.<o:p></o:p></span></li>
<li class="MsoNormal" style="background: white; line-height: normal; mso-list: l0 level1 lfo4; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto; tab-stops: list .5in;"><span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">Allows grant funding to be used
to enhance passenger manifest data so that rail passengers can be
identified in case of emergency.<o:p></o:p></span></li>
</ul>
<div class="MsoNormal" style="background: white; line-height: normal; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto;">
<span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";"><b>From a quick read
of the text of the bill, link from the Senator's website:</b><o:p></o:p></span></div>
<div class="MsoNormal" style="background: white; line-height: normal; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto;">
<span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">The vulnerability
assessment off surface transportation modes required of the bill must evaluate the vetting and security training of employees
in maritime transportation and other individuals with access to sensitive or
secure areas of transportation networks.<o:p></o:p></span></div>
<div class="MsoNormal" style="background: white; line-height: normal; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto;">
<span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">The Commandant of
the Coast Guard shall coordinate
with the Administrator (of the
TSA) to provide input
and other information regarding the vulnerabilities of and
risks to maritime facilities. <o:p></o:p></span></div>
<div class="MsoNormal" style="background: white; line-height: normal; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto;">
<span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";"><br /></span></div>
<div class="MsoNormal" style="background: white; line-height: normal; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto;">
<span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">RISK-BASED SECURITY
STRATEGY-<o:p></o:p></span></div>
<div class="MsoNormal" style="background: white; line-height: normal; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto;">
<span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">(1) In GENERAL - Not later
than 180 days after the date the security assessment
from subsection (a) is complete, the
Administrator shall use the
results of the assessment-<o:p></o:p></span></div>
<div class="MsoNormal" style="background: white; line-height: normal; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto; text-indent: .5in;">
<span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">(A) to develop
and implement a cross-cutting, risk-based security strategy
that includes<o:p></o:p></span></div>
<div class="MsoNormal" style="background: white; line-height: normal; margin-left: .5in; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto; text-indent: .5in;">
<span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">(i) all surface transportation modes; <o:p></o:p></span></div>
<div class="MsoNormal" style="background: white; line-height: normal; margin-left: 1.0in; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto;">
<span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">(ii) to the
extent the Transportation Security Administration provides support in maritime transportation
security efforts, maritime
transportation;<o:p></o:p></span></div>
<div class="MsoNormal" style="background: white; line-height: normal; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto; text-indent: .5in;">
<span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">(B) coordinate with the
Commandant of the Coast Guard-<o:p></o:p></span></div>
<div class="MsoNormal" style="background: white; line-height: normal; margin-left: 1.0in; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto;">
<span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">(i) to evaluate existing maritime
transportation security programs, policies, and initiatives for
consistency with the risk-based security strategy and, to the extent
practicable, avoid any unnecessary duplication of effort;<o:p></o:p></span></div>
<div class="MsoNormal" style="background: white; line-height: normal; margin-left: 1.0in; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto;">
<span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">(ii) to
ensure there are
no security gaps between jurisdictional
authorities that a threat can exploit to
cause harm;<o:p></o:p></span></div>
<div class="MsoNormal" style="background: white; line-height: normal; margin-left: 1.5in; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto; text-indent: -.5in;">
<span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">(iii) to determine the
extent to which stakeholder security
programs, policies, and
initiatives address the
vulnerabilities and risks to maritime transportation systems, identified
in subsection (a); and<o:p></o:p></span></div>
<div class="MsoNormal" style="background: white; line-height: normal; margin-left: 1.0in; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto;">
<span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">(iv) subject
to clauses (ii) and (iii), to mitigate each vulnerability and risk
to maritime transportation systems identified in subsection (a).<o:p></o:p></span></div>
<div class="MsoNormal" style="background: white; line-height: normal; margin-left: 1.0in; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto;">
<br /></div>
<div class="MsoNormal" style="background: white; line-height: normal; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto;">
<span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">180 days after
the date that the security assessment is completed, TSA shall submit to the
appropriate Congressional committees a report that includes, among other items,
any recommended changes
to the National Infrastructure
Protection Plan, the modal
annexes to the NIPP, or relevant surface or
maritime transportation security
programs, policies, or
initiatives.<o:p></o:p></span></div>
<div class="MsoNormal" style="background: white; line-height: normal; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto;">
<span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";"><br /></span></div>
<div class="MsoNormal" style="background: white; line-height: normal; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto;">
<span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">BUDGET
TRANSPARENCY - ln submitting the annual budget of
the United States
Government under Section 1105 of
title 81, United States Code, the President shall
clearly distinguish the resources requested for surface and maritime
transportation security from the resources
requested for aviation security.<o:p></o:p></span></div>
<div class="MsoNormal" style="background: white; line-height: normal; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto;">
<span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";"><br /></span></div>
<div class="MsoNormal" style="background: white; line-height: normal; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto;">
<span style="font-family: "Arial",sans-serif; font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">SURFACE
TRANSPORTATION SECURITY ADVISORY COMMITTEE - The TSA Administrator shall establish within
the TSA the Surface Transportation
Security Advisory Committee. Voting members to serve in a volunteer,
non-paid basis and consist of
representatives from associations
representing the modes of surface
transportation; labor organizations representing the modes; groups
representing the users of the modes, including asset manufacturers, as appropriate; relevant
law enforcement, first responders,
and security experts; and other
groups as the
Administrator considers appropriate.<o:p></o:p></span></div>
<br />
<div class="MsoNormal">
<br /></div>
Laurie Thomashttp://www.blogger.com/profile/16611719448125721800noreply@blogger.com0tag:blogger.com,1999:blog-1555376450970352963.post-8015706097393687942017-02-03T08:41:00.000-08:002017-02-03T08:42:19.127-08:00gCaptain Article Concerning the Impact of the President’s Order on Immigration and Travel on U.S. Shipping<div class="MsoNormal" style="line-height: normal; margin-bottom: 19.5pt;">
<span style="color: #222222; font-family: "arial" , sans-serif; font-size: 12.0pt;"> On Feb.
1, 2017, <i>gCaptain</i> printed a sobering
article concerning the impact of the president’s order on immigration and
travel on U.S. shipping, at http://gcaptain.com/trumps-immigration-ban-and-its-implications-for-the-maritime-industry/. The entire content of the article is
reprinted below, with permission. <o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: 19.5pt;">
<span style="color: #222222; font-family: "arial" , sans-serif; font-size: 12.0pt;">FSOs who foresee an upcoming ban-related
problem with mariners should immediately contact the local COTP for guidance.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: 19.5pt;">
<span style="color: #222222; font-family: "arial" , sans-serif; font-size: 12.0pt;">“President Trump’s Executive Order on
immigration and travel to the United States has immediate implications for
ships calling at U.S. ports, particularly those ships with crew members hailing
from any one of the seven countries whose citizens are banned under the order,
P&I clubs are warning.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: 19.5pt;">
<span style="color: #222222; font-family: "arial" , sans-serif; font-size: 12.0pt;">As the Executive Order bans entry into the US
for citizens from Syria, Yemen, Sudan, Somalia, Iraq, Iran and Libya for the
next 90 days, crewmembers aboard ships entering US waters who are citizens of
these countries will be denied entry to the US during this time, says The
Standard Club, a specialist marine and energy insurer. The club is telling its
members to anticipate that shore leave will be denied for those crewmembers and
that enhanced security of the ship, including the use of armed guards, may be
ordered by local immigration officials while the ship is in a U.S. port.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: 19.5pt;">
<span style="color: #222222; font-family: "arial" , sans-serif; font-size: 12.0pt;">At this time however, it is not believed that
ships carrying crew from these countries will be denied entry into U.S. ports,
The Standard Club said.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: 19.5pt;">
<span style="color: #222222; font-family: "arial" , sans-serif; font-size: 12.0pt;">The UK P&I Club offered similar guidance
to its members.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: 19.5pt;">
<span style="color: #222222; font-family: "arial" , sans-serif; font-size: 12.0pt;">“For the next 90 days crewmembers from Syria,
Yemen, Sudan, Somalia, Iraq, Iran and Libya, whether or not they hold visas,
will be denied entry to the U.S.,” the UK P&I Club wrote in a alert to
members. The club is warning members to avoid crew changes in the United States
for those citizens of the seven countries targeted by the order.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: 19.5pt;">
<span style="color: #222222; font-family: "arial" , sans-serif; font-size: 12.0pt;">Regarding medical emergencies, both the UK
P&I Club and The Standard Club say if a crewmember from Syria, Yemen,
Sudan, Somalia, Iraq, Iran and Libya requires emergency medical treatment while
in the United, there is an exception under the order that MAY allow the
crewmember to be removed from the ship for medical treatment.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: 19.5pt;">
<span style="color: #222222; font-family: "arial" , sans-serif; font-size: 12.0pt;">The Executive Order says that the Departments
of State and Homeland Security (CBP) may determine on a case by case basis to
issue visas or other immigration benefits to nationals of countries for which
visas and benefits are otherwise blocked. Therefore, government authorities may
be able to use the exception to allow the crewmember to be treated in the U.S.
if there is a true medical emergency.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: 19.5pt;">
<span style="color: #222222; font-family: "arial" , sans-serif; font-size: 12.0pt;">At this time it is unclear how many ships and
crew members may be impacted by the Executive Order.<o:p></o:p></span></div>
<div class="MsoNormal" style="line-height: normal; margin-bottom: 19.5pt;">
<span style="color: #222222; font-family: "arial" , sans-serif; font-size: 12.0pt;">Both the UK P&I Club and The Standard Club
say they will continue to monitor the situation and update its members with any
developments.<o:p></o:p></span></div>
<br />
<div class="MsoNormal" style="line-height: normal; margin-bottom: 19.5pt;">
<span style="color: #222222; font-family: "arial" , sans-serif; font-size: 12.0pt;">In addition to banning citizens from the seven
countries for 90 days, the Executive Order also bars the entry of refugees from
Syria indefinitely and stops admission of all refugees to the United States for
the next four months, among other things.”<o:p></o:p></span></div>
Laurie Thomashttp://www.blogger.com/profile/16611719448125721800noreply@blogger.com0tag:blogger.com,1999:blog-1555376450970352963.post-79203069332786648182017-01-27T09:47:00.000-08:002017-01-27T09:47:42.445-08:00 Final rule - Civil monetary penalties assessed by the USCG adjusted for inflation in today’s FR effective immediately for violations occurring after 11/02/2015<div class="MsoNormal">
<span style="background: white; color: #252525; font-family: "Arial",sans-serif; font-size: 10.5pt; line-height: 107%;">In the January 27, 2017
Federal Register, at <a href="https://www.gpo.gov/fdsys/pkg/FR-2017-01-27/pdf/2017-00605.pdf">https://www.gpo.gov/fdsys/pkg/FR-2017-01-27/pdf/2017-00605.pdf</a>,
the Department of Homeland Security established the schedule of civil monetary
penalties as adjusted for inflation. As explained in the Final Rule, in 2015
government agencies were required to “(1) Adjust the level of civil monetary
penalties with an initial ‘‘catch-up’’ adjustment through issuance of an
Interim Final Rule (IFR) and (2) make subsequent annual adjustments for
inflation”. This final rule reflects this adjustment, is effective immediately,
and applies to violations that occurred after November 2, 2015. <o:p></o:p></span></div>
<br />
<div class="MsoNormal">
<span style="background: white; color: #252525; font-family: "Arial",sans-serif; font-size: 10.5pt; line-height: 107%;">The Coast Guard has a
lengthy list of civil violation costs; port security appears near the end of
this list on p. 8577. Amending 46 U.S.C. 70119 (cited in 33 CFR 101.415,
Penalties) the new penalty for a port security violation is $33,333. The
penalty for a continuing violation is $59,893.<o:p></o:p></span></div>
Laurie Thomashttp://www.blogger.com/profile/16611719448125721800noreply@blogger.com0tag:blogger.com,1999:blog-1555376450970352963.post-47267243367127496112017-01-18T06:48:00.000-08:002017-01-18T06:48:40.516-08:00<div class="WordSection1">
<div class="MsoNormal">
<span style="font-family: "Arial",sans-serif;">On 01/17/2017,
the U.S. Coast Guard Maritime Commons site advised that the Coast Guard had
recently published CG-5P Policy Letter 08-16: Reporting Suspicious Activity and
Breaches of Security, which outlines the criteria and process for suspicious
activity (SA) and breach of security (BoS) reporting. http://mariners.coastguard.dodlive.mil/2017/01/17/cyber-reporting-updated-coast-guard-policy-reporting-suspicious-activity-breaches-security/<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: "Arial",sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: "Arial",sans-serif;">The document
can be found at Homeport >Maritime Security > Policy. The purpose of the policy
document, dated 12/14/2016, is to promulgate policy for use by MTSA-regulated
vessels and facilities outlining the criteria and process for suspicious
activity and breach of security reporting. Because plausible terrorist attack
scenarios include combined cyber and physical incidents, vessel and facility
operators should consider this possibility when evaluating a cyber incident,
including the possibility that a cyber incident is a precursor to a physical
attack. As a security measure, The Coast Guard strongly encourages vessel and
facility operators to minimize, monitor, and wherever possible, eliminate cyber
connections between the business/administrative systems and the operational,
industrial control and security systems. The USCG handles all reports of
security incidents as SSI.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: "Arial",sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: "Arial",sans-serif;">What is really
new in this policy document is:<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: "Arial",sans-serif;">1. Inclusion of cyber incidents into BoS and SA;<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: "Arial",sans-serif;">2. An expanded
definition of SA;<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: "Arial",sans-serif;">3. Permission
to report c</span><span style="font-family: Arial, sans-serif;">yber incidents to the</span> <span style="font-family: Arial, sans-serif;">National Cybersecurity and Communications Integration Center under certain </span><span style="font-family: Arial, sans-serif;">conditions</span></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
<span style="font-family: "Arial",sans-serif;">The document
then proceeds to describe U.S. Coast Guard requirements for reporting BoS and
SA for both physical and network or computer-related events. The inclusion of
cyber here is new and helpful. Industry has been reporting physical BoS and SA
since 2004 but cyber is much newer and many FSOs are less certain when to
report.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: "Arial",sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: "Arial",sans-serif;">Breaches of security
include:<o:p></o:p></span></div>
<div class="MsoListParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 105.0pt; margin-right: 9.95pt; margin-top: 6.0pt; mso-list: l2 level2 lfo1; tab-stops: 105.05pt;">
<!--[if !supportLists]--><span style="color: #231f20; font-size: 12.0pt; letter-spacing: -.05pt; mso-font-width: 99%;">a)<span style="font-size: 7pt; font-stretch: normal; font-variant-numeric: normal; line-height: normal;">
</span></span><!--[endif]--><span style="color: #231f20; font-family: "Arial",sans-serif;">“Intrusion into telecommunications equipment, computer, and
networked systems linked to security plan functions (e.g., access control,
cargo control, monitoring), unauthorized root or administrator access to
security and industrial control systems, successful phishing attempts or
malicious insider activity that could allow outside entities access to internal
IT systems that are linked to the<span style="letter-spacing: -.05pt;"> </span>MTS;</span><span style="font-family: "Arial",sans-serif;"><o:p></o:p></span></div>
<div class="MsoListParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 105.0pt; margin-right: 5.25pt; margin-top: 6.0pt; mso-list: l2 level2 lfo1; tab-stops: 105.05pt;">
<!--[if !supportLists]--><span style="color: #231f20; font-size: 12.0pt; letter-spacing: -.05pt; mso-font-width: 99%;">b)<span style="font-size: 7pt; font-stretch: normal; font-variant-numeric: normal; line-height: normal;">
</span></span><!--[endif]--><span style="color: #231f20; font-family: "Arial",sans-serif;">Instances of viruses, Trojan Horses, worms, zombies or other
malicious software that have a widespread impact or adversely affect one or
more on-site mission critical servers that are linked to security plan
functions;<span style="letter-spacing: -.15pt;"> </span>and/or</span><span style="font-family: "Arial",sans-serif;"><o:p></o:p></span></div>
<div class="MsoListParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 105.0pt; margin-right: 9.65pt; margin-top: 6.0pt; mso-list: l2 level2 lfo1; tab-stops: 105.1pt;">
<!--[if !supportLists]--><span style="color: #231f20; font-size: 12.0pt; letter-spacing: -.05pt; mso-font-width: 99%;">c)<span style="font-size: 7pt; font-stretch: normal; font-variant-numeric: normal; line-height: normal;">
</span></span><!--[endif]--><span style="color: #231f20; font-family: "Arial",sans-serif;">Any denial of service attacks that adversely affect or degrade
access to critical services that are linked to security plan<span style="letter-spacing: -1.8pt;"> </span>functions.</span><span style="font-family: "Arial",sans-serif;"><o:p></o:p></span></div>
<div class="MsoListParagraph" style="margin-right: 5.0pt; tab-stops: 79.95pt; text-indent: 0in;">
<span style="color: #231f20; font-family: "Arial",sans-serif;">Note that
routine spam, phishing attempts, and other nuisance events that do not breach a
system’s defenses are NOT BoS.
Furthermore, breaches of telecommunications equipment, computer, and
networked systems that clearly target business or administrative systems unrelated
to safe and secure maritime operations are outside the U.S. Coast Guard’s<span style="letter-spacing: -.35pt;"> </span>jurisdiction and need not be reported to
the U.S. Coast Guard.</span></div>
<div class="MsoListParagraph" style="margin-right: 5.0pt; tab-stops: 79.95pt; text-indent: 0in;">
<span style="color: #231f20; font-family: "Arial",sans-serif;"><br /></span></div>
<div class="MsoListParagraph" style="margin-right: 5.0pt; tab-stops: 79.95pt; text-indent: 0in;">
<span style="color: #231f20; font-family: "Arial",sans-serif;">Suspicious Activity includes:</span></div>
<div class="MsoListParagraph" style="margin-right: 5.0pt; tab-stops: 79.95pt; text-indent: -80.0pt;">
<br /></div>
<div class="MsoListParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 55.0pt; margin-right: 0in; margin-top: 0in; mso-list: l0 level2 lfo3; tab-stops: 55.05pt;">
<!--[if !supportLists]--><span style="color: #231f20; font-size: 12.0pt; mso-font-width: 99%;">A.<span style="font-size: 7pt; font-stretch: normal; font-variant-numeric: normal; line-height: normal;">
</span></span><!--[endif]--><u><span style="color: #231f20; font-family: "Arial",sans-serif;">Suspicious<span style="letter-spacing: -.1pt;"> </span>Activity</span></u><span style="font-family: "Arial",sans-serif;"><o:p></o:p></span></div>
<div class="MsoListParagraph" style="margin-right: 13.05pt; mso-list: l1 level1 lfo2; tab-stops: 79.95pt 80.0pt; text-indent: -25.05pt;">
<!--[if !supportLists]--><span style="color: #231f20; font-size: 12.0pt; letter-spacing: -.15pt; mso-font-width: 99%;">i.<span style="font-size: 7pt; font-stretch: normal; font-variant-numeric: normal; line-height: normal;">
</span></span><!--[endif]--><span style="color: #231f20; font-family: "Arial",sans-serif;">Reference (c) defines SA as “<u>observed
</u>behavior reasonably indicative of pre-operational planning related to
terrorism or other criminal<span style="letter-spacing: -.35pt;"> </span>activity.”</span><span style="font-family: "Arial",sans-serif;"><o:p></o:p></span></div>
<div class="MsoListParagraph" style="margin-right: 16.3pt; mso-list: l1 level1 lfo2; tab-stops: 79.95pt 80.0pt; text-indent: -25.05pt;">
<!--[if !supportLists]--><span style="color: #231f20; font-size: 12.0pt; letter-spacing: -.15pt; mso-font-width: 99%;">ii.<span style="font-size: 7pt; font-stretch: normal; font-variant-numeric: normal; line-height: normal;">
</span></span><!--[endif]--><span style="color: #231f20; font-family: "Arial",sans-serif;">Computer-related suspicious activity presents additional
vulnerabilities, and companies should be able to distinguish untargeted cyber
incidents from targeted incidents on vessel or waterfront facility computer
related systems. Untargeted cyber incidents are part of the normal information
technology landscape and commonly include “phishing” or persistent scanning of
networks, and these are not considered SA or<span style="letter-spacing: -.15pt;">
</span>BoS.</span><span style="font-family: "Arial",sans-serif;"><o:p></o:p></span></div>
<div class="MsoListParagraph" style="margin-right: 15.6pt; mso-list: l1 level1 lfo2; tab-stops: 79.95pt; text-indent: -25.05pt;">
<!--[if !supportLists]--><span style="color: #231f20; font-size: 12.0pt; letter-spacing: -.15pt; mso-font-width: 99%;">iii.<span style="font-size: 7pt; font-stretch: normal; font-variant-numeric: normal; line-height: normal;">
</span></span><!--[endif]--><span style="color: #231f20; font-family: "Arial",sans-serif;">In contrast, targeted incidents may be large, sustained attacks
on important cyber systems in an apparent attempt to exploit them for nefarious
purposes. Spear phishing campaigns, a marked increase in network scanning, or
other attacks may be considered SA if the volume, persistence, or
sophistication of the attacks is out of the<span style="letter-spacing: -.5pt;"> </span>ordinary.</span><span style="font-family: "Arial",sans-serif;"><o:p></o:p></span></div>
<div class="MsoListParagraph" style="margin-right: 5.9pt; mso-list: l1 level1 lfo2; tab-stops: 79.95pt 80.0pt; text-indent: -25.05pt;">
<!--[if !supportLists]--><span style="color: #231f20; font-size: 12.0pt; letter-spacing: -.15pt; mso-font-width: 99%;">iv.<span style="font-size: 7pt; font-stretch: normal; font-variant-numeric: normal; line-height: normal;">
</span></span><!--[endif]--><span style="color: #231f20; font-family: "Arial",sans-serif;">Unsuccessful but apparently targeted incidents may be SA if they
threaten systems that could contribute to a TSI, have a link to the MTS portion
of the facility or are otherwise related to systems, personnel, and procedures
addressed by security plans or MTSA<span style="letter-spacing: -.35pt;"> </span>requirements.</span><span style="font-family: "Arial",sans-serif;"><o:p></o:p></span></div>
<div class="MsoListParagraph" style="mso-list: l1 level1 lfo2; tab-stops: 79.95pt 80.05pt; text-indent: -25.05pt;">
<!--[if !supportLists]--><span style="color: #231f20; font-size: 12.0pt; letter-spacing: -.15pt; mso-font-width: 99%;">v.<span style="font-size: 7pt; font-stretch: normal; font-variant-numeric: normal; line-height: normal;">
</span></span><!--[endif]--><span style="color: #231f20; font-family: "Arial",sans-serif;">SA may include, but is not limited to, any of the<span style="letter-spacing: -.35pt;"> </span>following:</span><span style="font-family: "Arial",sans-serif;"><o:p></o:p></span></div>
<div class="MsoListParagraph" style="margin-left: 105.0pt; mso-list: l1 level2 lfo2; tab-stops: 105.05pt;">
<!--[if !supportLists]--><span style="color: #231f20; font-size: 12.0pt; letter-spacing: -.1pt; mso-font-width: 99%;">a)<span style="font-size: 7pt; font-stretch: normal; font-variant-numeric: normal; line-height: normal;">
</span></span><!--[endif]--><span style="color: #231f20; font-family: "Arial",sans-serif;">Unfamiliar persons in areas that are restricted to regular<span style="letter-spacing: -.65pt;"> </span>employees;</span><span style="font-family: "Arial",sans-serif;"><o:p></o:p></span></div>
<div class="MsoListParagraph" style="margin-left: 105.0pt; mso-list: l1 level2 lfo2; tab-stops: 105.05pt;">
<!--[if !supportLists]--><span style="color: #231f20; font-size: 12.0pt; letter-spacing: -.1pt; mso-font-width: 99%;">b)<span style="font-size: 7pt; font-stretch: normal; font-variant-numeric: normal; line-height: normal;">
</span></span><!--[endif]--><span style="color: #231f20; font-family: "Arial",sans-serif;">Unusual behavioral patterns, such<span style="letter-spacing: -.05pt;"> </span>as:</span><span style="font-family: "Arial",sans-serif;"><o:p></o:p></span></div>
</div>
<span style="font-family: "Arial",sans-serif; font-size: 11.0pt; line-height: 107%; mso-ansi-language: EN-US; mso-bidi-language: AR-SA; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin;"><br clear="all" style="mso-break-type: section-break; page-break-before: always;" />
</span>
<br />
<div class="WordSection2">
<div class="MsoBodyText" style="margin-top: 0in;">
<br /></div>
<div class="MsoListParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 129.95pt; margin-right: 0in; margin-top: 3.45pt; mso-list: l1 level3 lfo2; tab-stops: 129.95pt 130.0pt; text-indent: -24.95pt;">
<!--[if !supportLists]--><span style="color: #231f20; font-size: 12.0pt; letter-spacing: -.1pt; mso-font-width: 99%;">(1)<span style="font-size: 7pt; font-stretch: normal; font-variant-numeric: normal; line-height: normal;">
</span></span><!--[endif]--><span style="color: #231f20; font-family: "Arial",sans-serif;">Not responding to verbal<span style="letter-spacing: -.15pt;"> </span>interaction;</span><span style="font-family: "Arial",sans-serif;"><o:p></o:p></span></div>
<div class="MsoListParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 129.95pt; margin-right: 31.85pt; margin-top: 6.0pt; mso-list: l1 level3 lfo2; tab-stops: 129.95pt 130.0pt; text-indent: -24.95pt;">
<!--[if !supportLists]--><span style="color: #231f20; font-size: 12.0pt; letter-spacing: -.1pt; mso-font-width: 99%;">(2)<span style="font-size: 7pt; font-stretch: normal; font-variant-numeric: normal; line-height: normal;">
</span></span><!--[endif]--><span style="color: #231f20; font-family: "Arial",sans-serif;">Walking slowly in a deliberate fashion towards a potential
target;</span><span style="font-family: "Arial",sans-serif;"><o:p></o:p></span></div>
<div class="MsoListParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 129.95pt; margin-right: 13.35pt; margin-top: 6.0pt; mso-list: l1 level3 lfo2; tab-stops: 129.95pt 130.0pt; text-indent: -24.95pt;">
<!--[if !supportLists]--><span style="color: #231f20; font-size: 12.0pt; letter-spacing: -.1pt; mso-font-width: 99%;">(3)<span style="font-size: 7pt; font-stretch: normal; font-variant-numeric: normal; line-height: normal;">
</span></span><!--[endif]--><span style="color: #231f20; font-family: "Arial",sans-serif;">Inappropriately dressed (e.g., wearing excessive clothing as to
conceal something, or looking out of<span style="letter-spacing: -.4pt;"> </span>place);</span><span style="font-family: "Arial",sans-serif;"><o:p></o:p></span></div>
<div class="MsoListParagraph" style="margin-left: 129.95pt; mso-list: l1 level3 lfo2; tab-stops: 129.95pt 130.0pt; text-indent: -24.95pt;">
<!--[if !supportLists]--><span style="color: #231f20; font-size: 12.0pt; letter-spacing: -.1pt; mso-font-width: 99%;">(4)<span style="font-size: 7pt; font-stretch: normal; font-variant-numeric: normal; line-height: normal;">
</span></span><!--[endif]--><span style="color: #231f20; font-family: "Arial",sans-serif;">Excessive nervousness or “doomsday”<span style="letter-spacing: -.35pt;"> </span>talk;</span><span style="font-family: "Arial",sans-serif;"><o:p></o:p></span></div>
<div class="MsoListParagraph" style="margin-left: 129.95pt; mso-list: l1 level3 lfo2; tab-stops: 129.95pt 130.0pt; text-indent: -24.95pt;">
<!--[if !supportLists]--><span style="color: #231f20; font-size: 12.0pt; letter-spacing: -.1pt; mso-font-width: 99%;">(5)<span style="font-size: 7pt; font-stretch: normal; font-variant-numeric: normal; line-height: normal;">
</span></span><!--[endif]--><span style="color: #231f20; font-family: "Arial",sans-serif;">Excessive<span style="letter-spacing: -.1pt;"> </span>questions;</span><span style="font-family: "Arial",sans-serif;"><o:p></o:p></span></div>
<div class="MsoListParagraph" style="margin-left: 129.95pt; mso-list: l1 level3 lfo2; tab-stops: 129.95pt 130.0pt; text-indent: -24.95pt;">
<!--[if !supportLists]--><span style="color: #231f20; font-size: 12.0pt; letter-spacing: -.1pt; mso-font-width: 99%;">(6)<span style="font-size: 7pt; font-stretch: normal; font-variant-numeric: normal; line-height: normal;">
</span></span><!--[endif]--><span style="color: #231f20; font-family: "Arial",sans-serif;">Lack of photo<span style="letter-spacing: -.05pt;"> </span>identification;</span><span style="font-family: "Arial",sans-serif;"><o:p></o:p></span></div>
<div class="MsoListParagraph" style="margin-left: 129.95pt; mso-list: l1 level3 lfo2; tab-stops: 129.95pt 130.0pt; text-indent: -24.95pt;">
<!--[if !supportLists]--><span style="color: #231f20; font-size: 12.0pt; letter-spacing: -.1pt; mso-font-width: 99%;">(7)<span style="font-size: 7pt; font-stretch: normal; font-variant-numeric: normal; line-height: normal;">
</span></span><!--[endif]--><span style="color: #231f20; font-family: "Arial",sans-serif;">Agitation or<span style="letter-spacing: -.15pt;"> </span>rage;</span><span style="font-family: "Arial",sans-serif;"><o:p></o:p></span></div>
<div class="MsoListParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 129.95pt; margin-right: 16.0pt; margin-top: 6.0pt; mso-list: l1 level3 lfo2; tab-stops: 129.95pt 130.0pt; text-indent: -24.95pt;">
<!--[if !supportLists]--><span style="color: #231f20; font-size: 12.0pt; letter-spacing: -.1pt; mso-font-width: 99%;">(8)<span style="font-size: 7pt; font-stretch: normal; font-variant-numeric: normal; line-height: normal;">
</span></span><!--[endif]--><span style="color: #231f20; font-family: "Arial",sans-serif;">Picture taking, especially if the suspect has been asked earlier
not to take<span style="letter-spacing: -.55pt;"> </span>photos;</span><span style="font-family: "Arial",sans-serif;"><o:p></o:p></span></div>
<div class="MsoListParagraph" style="margin-left: 129.95pt; mso-list: l1 level3 lfo2; tab-stops: 129.95pt 130.0pt; text-indent: -24.95pt;">
<!--[if !supportLists]--><span style="color: #231f20; font-size: 12.0pt; letter-spacing: -.1pt; mso-font-width: 99%;">(9)<span style="font-size: 7pt; font-stretch: normal; font-variant-numeric: normal; line-height: normal;">
</span></span><!--[endif]--><span style="color: #231f20; font-family: "Arial",sans-serif;">Note taking or<span style="letter-spacing: -.2pt;"> </span>drawing;</span><span style="font-family: "Arial",sans-serif;"><o:p></o:p></span></div>
<div class="MsoListParagraph" style="margin-left: 129.95pt; mso-list: l1 level3 lfo2; tab-stops: 130.0pt; text-indent: -24.95pt;">
<!--[if !supportLists]--><span style="color: #231f20; font-size: 12.0pt; letter-spacing: -.1pt; mso-font-width: 99%;">(10)<span style="font-size: 7pt; font-stretch: normal; font-variant-numeric: normal; line-height: normal;">
</span></span><!--[endif]--><span style="color: #231f20; font-family: "Arial",sans-serif;">Taking measurements;<span style="letter-spacing: -.2pt;"> </span>and/or</span><span style="font-family: "Arial",sans-serif;"><o:p></o:p></span></div>
<div class="MsoListParagraph" style="margin-left: 129.95pt; mso-list: l1 level3 lfo2; tab-stops: 130.0pt; text-indent: -24.95pt;">
<!--[if !supportLists]--><span style="color: #231f20; font-size: 12.0pt; letter-spacing: -.1pt; mso-font-width: 99%;">(11)<span style="font-size: 7pt; font-stretch: normal; font-variant-numeric: normal; line-height: normal;">
</span></span><!--[endif]--><span style="color: #231f20; font-family: "Arial",sans-serif;">Attempting to access unauthorized<span style="letter-spacing: -.25pt;"> </span>areas.</span><span style="font-family: "Arial",sans-serif;"><o:p></o:p></span></div>
<div class="MsoListParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 105.0pt; margin-right: 11.45pt; margin-top: 6.0pt; mso-list: l1 level2 lfo2; tab-stops: 105.05pt;">
<!--[if !supportLists]--><span style="color: #231f20; font-size: 12.0pt; letter-spacing: -.1pt; mso-font-width: 99%;">c)<span style="font-size: 7pt; font-stretch: normal; font-variant-numeric: normal; line-height: normal;">
</span></span><!--[endif]--><span style="color: #231f20; font-family: "Arial",sans-serif;">Potentially dangerous devices found by screeners prior to
loading persons or cargo or items found on or near the facility that seem<span style="letter-spacing: -.65pt;"> </span>out of place.</span><span style="font-family: "Arial",sans-serif;"><o:p></o:p></span></div>
<div class="MsoListParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 105.0pt; margin-right: 14.25pt; margin-top: 6.0pt; mso-list: l1 level2 lfo2; tab-stops: 105.05pt;">
<!--[if !supportLists]--><span style="color: #231f20; font-size: 12.0pt; letter-spacing: -.1pt; mso-font-width: 99%;">d)<span style="font-size: 7pt; font-stretch: normal; font-variant-numeric: normal; line-height: normal;">
</span></span><!--[endif]--><span style="color: #231f20; font-family: "Arial",sans-serif;">Vehicles parked or standing for excessive amounts of time near
the facility<span style="letter-spacing: -.1pt;"> </span>perimeter;</span><span style="font-family: "Arial",sans-serif;"><o:p></o:p></span></div>
<div class="MsoListParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 105.0pt; margin-right: 5.8pt; margin-top: 6.0pt; mso-list: l1 level2 lfo2; tab-stops: 105.05pt;">
<!--[if !supportLists]--><span style="color: #231f20; font-size: 12.0pt; letter-spacing: -.1pt; mso-font-width: 99%;">e)<span style="font-size: 7pt; font-stretch: normal; font-variant-numeric: normal; line-height: normal;">
</span></span><!--[endif]--><span style="color: #231f20; font-family: "Arial",sans-serif;">Unmanned Aircraft System (UAS) activity, including but not
limited to:</span><span style="font-family: "Arial",sans-serif;"><o:p></o:p></span></div>
<div class="MsoListParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 129.95pt; margin-right: 6.25pt; margin-top: 6.0pt; mso-list: l1 level3 lfo2; tab-stops: 129.95pt 130.0pt; text-indent: -24.95pt;">
<!--[if !supportLists]--><span style="color: #231f20; font-size: 12.0pt; letter-spacing: -.1pt; mso-font-width: 99%;">(1)<span style="font-size: 7pt; font-stretch: normal; font-variant-numeric: normal; line-height: normal;">
</span></span><!--[endif]--><span style="color: #231f20; font-family: "Arial",sans-serif;">Reconnaissance and surveillance activities, indicated by
repeated activities at a particular place and time (e.g., fly-overs, hovering
at low altitudes, and prolonged time on station); and/or</span><span style="font-family: "Arial",sans-serif;"><o:p></o:p></span></div>
<div class="MsoListParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 129.95pt; margin-right: 16.25pt; margin-top: 6.0pt; mso-list: l1 level3 lfo2; tab-stops: 129.95pt 130.0pt; text-indent: -24.95pt;">
<!--[if !supportLists]--><span style="color: #231f20; font-size: 12.0pt; letter-spacing: -.1pt; mso-font-width: 99%;">(2)<span style="font-size: 7pt; font-stretch: normal; font-variant-numeric: normal; line-height: normal;">
</span></span><!--[endif]--><span style="color: #231f20; font-family: "Arial",sans-serif;">Testing of facility security protocols using UAS, indicated by
flying by a target, moving into sensitive areas, and observing the reaction of
security personnel (e.g., the time it takes to respond to an incident or the
routes taken to a specific location).</span><span style="font-family: "Arial",sans-serif;"><o:p></o:p></span></div>
<div class="MsoListParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 105.0pt; margin-right: 14.2pt; margin-top: 6.0pt; mso-list: l1 level2 lfo2; tab-stops: 105.1pt;">
<!--[if !supportLists]--><span style="color: #231f20; font-size: 12.0pt; letter-spacing: -.1pt; mso-font-width: 99%;">f)<span style="font-size: 7pt; font-stretch: normal; font-variant-numeric: normal; line-height: normal;">
</span></span><!--[endif]--><span style="color: #231f20; font-family: "Arial",sans-serif;">Unauthorized personnel accessing IT spaces linked to security
plan functions.</span><span style="font-family: "Arial",sans-serif;"><o:p></o:p></span></div>
<div class="MsoListParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 105.0pt; margin-right: 13.55pt; margin-top: 6.0pt; mso-list: l1 level2 lfo2; tab-stops: 105.05pt;">
<!--[if !supportLists]--><span style="color: #231f20; font-size: 12.0pt; letter-spacing: -.1pt; mso-font-width: 99%;">g)<span style="font-size: 7pt; font-stretch: normal; font-variant-numeric: normal; line-height: normal;">
</span></span><!--[endif]--><span style="color: #231f20; font-family: "Arial",sans-serif;">Unsuccessful attempts to access telecommunication, computer, and
network systems linked to security plan<span style="letter-spacing: -.15pt;"> </span>functions.</span><span style="font-family: "Arial",sans-serif;"><o:p></o:p></span></div>
<div class="MsoListParagraph" style="margin-right: 15.8pt; mso-list: l1 level1 lfo2; tab-stops: 79.95pt 80.0pt; text-indent: -25.05pt;">
<!--[if !supportLists]--><span style="color: #231f20; font-size: 12.0pt; letter-spacing: -.15pt; mso-font-width: 99%;">vi.<span style="font-size: 7pt; font-stretch: normal; font-variant-numeric: normal; line-height: normal;">
</span></span><!--[endif]--><span style="color: #231f20; font-family: "Arial",sans-serif;">The Coast Guard recognizes that the cyber domain includes
countless malicious but low-level events that are normally addressed via
standard anti-virus programs and similar protocols. Operators should only
report events that are out of the ordinary in terms of sophistication, volume,
or other factors which, from the operator’s perspective, raise<span style="letter-spacing: -.4pt;"> </span>suspicions.</span><span style="font-family: "Arial",sans-serif;"><o:p></o:p></span></div>
</div>
<span style="font-family: "Calibri",sans-serif; font-size: 12.0pt; line-height: 107%; mso-ansi-language: EN-US; mso-ascii-theme-font: minor-latin; mso-bidi-font-family: "Times New Roman"; mso-bidi-font-size: 11.0pt; mso-bidi-language: AR-SA; mso-bidi-theme-font: minor-bidi; mso-fareast-font-family: Calibri; mso-fareast-language: EN-US; mso-fareast-theme-font: minor-latin; mso-hansi-theme-font: minor-latin;"><br clear="all" style="mso-break-type: section-break; page-break-before: always;" />
</span>
<br />
<div class="MsoNormal">
<span style="font-family: "Arial",sans-serif;">Cyber incidents
may be reported to the</span> <span style="font-family: "Arial",sans-serif;">National
Cybersecurity and Communications Integration Center. <b><i><u>It is imperative that the
reporting party inform the NCCIC that they are a Coast Guard regulated entity
in order to satisfy the reporting requirements of 33 CFR part 101.305.</u></i></b>
The NCCIC will forward the report electronically to the NRC, who will notify
the appropriate COTP.</span> <span style="font-family: "Arial",sans-serif;">Reporting
cyber incidents in this manner, including notifying the NCCIC that the
reporting source is regulated by the Coast Guard, meets Coast Guard regulatory
requirements. Note that this is applicable for only a cyber incident; if there
are other factors involved, such as pollution or a physical breach of security,
operators must report the incident directly to the NRC.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: "Arial",sans-serif;"><br /></span></div>
<br />
<div class="MsoNormal">
<span style="font-family: "Arial",sans-serif;">The policy
document then discusses other Critical Infrastructure and Cyber Incident resources,
including ICS-CERT, InfraGard, National Suspicious Activity Reporting (SAR)
Initiative, and the local AMSC.<o:p></o:p></span></div>
Laurie Thomashttp://www.blogger.com/profile/16611719448125721800noreply@blogger.com0tag:blogger.com,1999:blog-1555376450970352963.post-17827454500967450202016-04-13T08:52:00.000-07:002016-04-13T08:53:53.465-07:00HR 3586 Sec. 12, TWIC Provisions<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;">Our colleague Patrick Coyle at Chemical Facility Security
News (<a href="http://chemical-facility-security-news.blogspot.com/2016/04/house-to-consider-hr-3586-today.html">http://chemical-facility-security-news.blogspot.com/2016/04/house-to-consider-hr-3586-today.html</a>)
spotted and posted about HR 3586, To amend the Homeland Security Act of 2002 to
improve border and maritime security coordination in the Department of Homeland
Security, and for other purposes. The bill is at https://www.congress.gov/114/bills/hr3586/BILLS-114hr3586rh.pdf<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;">Mr. Coyle expects that the bill will pass with substantial
bipartisan support today, and will probably be taken up by the Senate under
their unanimous consent process, without debate and no vote. A discussion of
the TWIC provisions is below, followed by the full text of Sec. 12, the section
dealing with TWIC.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;">The bill requires DHS to publish a list of documents that
will identify non-United States citizen
TWIC applicants and verify the immigration statuses of such applicants by
requiring each such applicant to produce a document or documents that demonstrate (i) identity;
and (ii) proof of lawful presence in the
United States. The bill also requires DHS to enhance training requirements to
ensure that trusted agents at transportation security card enrollment centers
receive training to identify fraudulent documents.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;">There are two parts to Sec. 12: #1, strengthening procedures so that the card
cannot be used by illegal aliens and #2, requiring a report from DHS on the
appeals process. (The section title states “waiver and appeals” but only the
appeal process is addressed in the bill and the two processes are entirely
apples and oranges. I don’t have any figures and this is just an informed guess
but I am betting that there are many more waivers filed than appeals.)<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;">It is unclear what else DHS needs to do to about non-United
States citizen TWIC applicants. There is already a procedure in place for
foreign nationals who need a TWIC. They need to obtain a TWIC-annotated B-1
visa. From the TSA TWIC website:<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;">“What is the TWIC annotated B-1 visa and who can apply for
one?<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;">Foreign nationals who perform maritime services in the
United States and require access to secure areas of facilities and vessels can
apply for this type of B-1 visa, specifically designed for the TWIC program.
These individuals are required to meet the eligibility requirements set forth
by the Department of State for a B-1 visa (‘Temporary Visitor for Business’)
and are required to provide an official letter from their employer stating that
a TWIC is required to perform the individual’s job in the maritime industry.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;">This letter must be provided to the relevant U.S. Embassy or
Consulate as part of the individual’s visa application. The employer letter
must contain details such as the type of work performed by the individual, the
location and duration of the work, as well as employer contact information is
required if additional information or follow up is necessary.”<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;">NLT 90 days after the bill is passed, DHS must provide to the
Committee on Homeland Security of the House of Representatives and the
Committee on Commerce, Science, and Transportation of the Senate information on
(1) The average time for the completion
of an appeal under the appeals process; (2) The most common reasons for any
delays at each step in such process; (3)
Recommendations on how to resolve any such delays as expeditiously as possible.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;">Text of this section:<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;">SEC. 12. TRANSPORTATION WORKER IDENTIFICATION CREDENTIAL
WAIVER AND APPEALS PROCESS. <o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;">(a) IN GENERAL.—Section 70105 of title 46, United 18 States
Code, is amended by adding at the end the following new section: <o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;"> ‘‘(r) SECURING THE TRANSPORTATION
WORKER IDENTIFICATION CREDENTIAL AGAINST USE BY UNAUTHORIZED ALIENS.— <o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;">‘‘(1) IN GENERAL.—The Secretary, acting through the Administrator of the
Transportation Security Administration, shall seek to strengthen the integrity
of transportation security cards issued under this section against improper
access by an individual who is not lawfully present in the United States. <o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;">‘‘(2) COMPONENTS.—In carrying out subsection (a), the Administrator of the Transportation
Security Administration shall— <o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;"> ‘‘(A) publish a list
of documents that will identify
non-United States citizen transportation security card applicants and verify
the immigration statuses of such applicants by requiring each such applicant to
produce a document or documents that
demonstrate— <o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;">‘‘(i) identity; and <o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;">‘‘(ii) proof of lawful presence in the United States; and</span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;"> ‘‘(B) enhance
training requirements to ensure that trusted agents at transportation security
card enrollment centers receive training to identify fraudulent documents. <o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;"> ‘‘(3) EXPIRATION.—A
transportation security card issued
under this section expires on the date of its expiration or on the date on which the
individual to whom such card is issued
is no longer lawfully entitled to be present in the United States, whichever is
earlier.’’. <o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;">(b) REPORT.—Not later than 90 days after the date of the
enactment of this Act, the Secretary of Homeland Security shall provide to the
Committee on Homeland Security of the House of Representatives and the
Committee on Commerce, Science, and Transportation of the Senate information on
the following:<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;"> (1) The average time
for the completion of an appeal under the appeals process established pursuant to
paragraph (4) of subsection (c) of section 70105 of title 46, United States
Code. <o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;">(2) The most common reasons for any delays at each step in
such process. <o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: "arial" , "helvetica" , sans-serif;">(3) Recommendations on how to resolve any such delays as
expeditiously as possible.</span><o:p></o:p></div>
<div class="MsoNormal">
<br /></div>
<br />
<div class="MsoNormal">
<br /></div>
Laurie Thomashttp://www.blogger.com/profile/16611719448125721800noreply@blogger.com0tag:blogger.com,1999:blog-1555376450970352963.post-41865948684371668212016-03-15T07:18:00.000-07:002016-03-15T07:18:31.198-07:00Troubling DHS Analysis of an Unexpected Closure of the Poe Lock and Its Impact<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">The
Department of Homeland Security, National Protection and Programs Directorate,
Office of Cyber and Infrastructure Analysis (OCIA-NISAC), has released “The Perils of Efficiency: An
Analysis of an Unexpected Closure of the Poe Lock and Its Impact.” We wish to thank the Principal Investigator Craig
S. Gordon, PhD and Supporting Investigator Marilee Orr for this disturbing but truly
important document, and for the editors of Seaway Review and the Lake Carriers
Association for making the report easily accessible. Below is a summary,
derived from the report, which can be found at http://www.lcaships.com/wp-content/uploads/2016/03/OCIA-The-Perils-of-Efficiency-An-Analysis-of-an-Unexpected-Closure-of-the-Poe-Lock-and-Its-Impact1.pdf. </span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">"The Soo Locks, which are owned and operated by the United States Army Corps of Engineers (USACE), consists </span><span style="font-family: Arial, Helvetica, sans-serif;">of four lock.The two primary locks in operation are the Poe Lock, rebuilt in 1968, and the </span><span style="font-family: Arial, Helvetica, sans-serif;">MacArthur Lock, constructed in 1943.The Lakers carrying iron ore use the Poe Lock almost exclusively because </span><span style="font-family: Arial, Helvetica, sans-serif;">the MacArthur Lock is too small to accommodate the larger Lakers; almost 70 percent of the U.S. Laker capacity </span><span style="font-family: Arial, Helvetica, sans-serif;">on the Great Lakes is Poe-restricted, meaning that the Lakers can use only the Poe Lock. Lakers small enough to </span><span style="font-family: Arial, Helvetica, sans-serif;">lock through the MacArthur Lock are referred, herein, as MacArthur-sized. The dependency on the Poe Locks to </span><span style="font-family: Arial, Helvetica, sans-serif;">move the preponderance of the commodities, particularly iron ore, led USACE to call the Poe Lock “the Achilles’ </span><span style="font-family: Arial, Helvetica, sans-serif;">heel of the Great Lakes Navigation System. There is currently no redundancy for the Poe Lock.”34 This lock is the </span><span style="font-family: Arial, Helvetica, sans-serif;">weak link in Great Lakes commerce.</span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">The scenario
closure used in the analysis lasts from March 25– September 25. Overall, about
78 percent of the domestic iron ore capacity is expected to shutter for the
duration of the scenario. Limestone deliveries could continue if only the Poe
Lock closed. Far less limestone is required to move upstream, </span><span style="font-family: Arial, Helvetica, sans-serif;">as the iron
ore-to-limestone ratio is about 9:1. </span><span style="font-family: Arial, Helvetica, sans-serif;"> </span><span style="font-family: Arial, Helvetica, sans-serif;">Further, limestone is far less dense than iron
ore and there are more options to deliver limestone to the pelletizing plant.</span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">An extended
closure of the Poe Lock, which OCIA-NISAC assumes to be 6-months, would be
extremely detrimental to the North American automotive industry including
Canada and Mexico. Almost all North American automobile production would cease,
and, in addition to the automotive industry, other industries that depend on steel
including farm, mining, and construction equipment manufacturing, railroad locomotive
and railcar production, and appliances.<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">According to industry experts, short-term disruptions of a
single steel mill can cause disruptions throughout the North American supply
chain. Firms must scramble to find alternative suppliers and to begin managing
the process, part-by-part, to extend production times for at least some of
their lines. Eventually, keeping the system going becomes impossible and lines
shut down due to the lack of a single component. It could take more than 2
months to resupply the supply chain with enough steel-based product to restart
production from the loss of a single steel mill. Lead times for many automotive
parts are typically 8 – 14 weeks. However, regarding the current scenario, one
industry expert said, "it's all done if all of the steel mills shut
down."<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt;">
<span style="font-family: Arial, Helvetica, sans-serif;">A 6-month closure, from about March 25 to September 25 does not mean
that steel production could begin shortly thereafter. First, blast furnaces,
which presumably have been hot idled or kept warm during the closure, would
have to be re-inspected. Extended hot idling can damage or destroy a blast
furnace, incurring lengthy repairs times and costs well in excess of $100
million each, though processes have improved that could mitigate this risk. A
significant problem with hot-idling a blast furnace is the cooling water. Hot
idling a blast furnace during the winter may lead to the freezing of the
cooling water and damage to the blast furnace. Blast furnaces generally operate
continuously for about 15 years between significant maintenance periods. If a blast
furnace is not going to be operated, it must </span><span style="font-family: Arial, Helvetica, sans-serif;">be kept warm by keeping coking coal heated, but not adding in iron ore,
limestone and enriched oxygen that make steel. Hot idling, the term to denote
this process of keeping the furnace warm is usually not done for periods longer
than a few weeks (see Platts, “Platts Steel Glossary,” at</span></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt;">
<span style="font-family: Arial, Helvetica, sans-serif;">www.steelbb.com/steelglossary/#term_206, accessed January 17, 2015).
Anything longer than a few weeks is considered, herein, to be an extended
period.<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt;">
<span style="font-family: Arial, Helvetica, sans-serif;">More problematic than re-starting the blast furnace is restarting the
coke batteries. C</span><span style="font-family: Arial, Helvetica, sans-serif;">oke batteries concentrate the carbon from coal to
make coke, which is an essential ingredient in steelmaking. Industry executives
reported that the coke battery must be operated continuously or hot-idled
properly to prevent damage. The coke battery is far more likely than the blast
furnace to become damaged in this unanticipated outage scenario. OCIA-NISAC
analysts believe that the steel mills will not re-commence mill operations
until about mid-December, </span><span style="font-family: Arial, Helvetica, sans-serif;">in order to secure sufficient inventory of iron ore to last through the
normal winter closure of the Soo Locks. Automotive parts manufacturers could
then begin operations in mid-January, but the first cars are not likely to come
off production lines until early April.</span><span style="font-family: Arial, Helvetica, sans-serif;"> </span></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt;">
<span style="font-family: Arial, Helvetica, sans-serif;">The scenario closure would have catastrophic impacts on the regional
and National economy. Economic modeling based on the assumptions described in
the preceding section shows that approximately $1.1 trillion in economic output,
as measured by the Gross Domestic Product (GDP), and over 10.9 million jobs
would be lost in the first year following the disruption. The impacts described
here are more severe than those predicted in prior studies because this
analysis took a comprehensive view of the supply chain and its relationship to
the National economy.<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt;">
<span style="font-family: Arial, Helvetica, sans-serif;">A 6-month closure of the Poe Lock, at the start of the navigation
season, would be expected to halt all automobile production and the sales of
cars manufactured in North America completely for almost 10 months, from about June
1 to April 1. That is, no automobiles would be produced in North America. By
comparison, during the 2009 recession, two of the three major automotive
companies required bailouts from the United States Government when annualized
sales of new automobiles had dropped from the typical 16–18 million units to
about 9 million units.<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt;">
<span style="font-family: Arial, Helvetica, sans-serif;">At the National level, the model predicts that the Poe Lock closure
scenario would add 5.8 percentage points to the unemployment rate, currently at
5.5 percent. This would bring the National unemployment rate under the closure
scenario to 11.3 percent. This would exceed the highest level of National
unemployment recorded during the 2008-2009 recession, which peaked at 10.0
percent in October 2009. Under the Poe Lock closure scenario, exceptionally high
rates of unemployment occur along the Great Lakes and south. Unemployment rates
in Indiana and Michigan would reach or exceed 22 percent and all of the Great
Lakes States, except for Minnesota and New York, have unemployment rates that
would exceed 10 percent.<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt;">
<span style="font-family: Arial, Helvetica, sans-serif;">A recession brought about by an unexpected closure of the Poe Lock
would be categorically different from historical recessions. Recessions are
usually caused by falling aggregate demand, credit contractions, or oil supply shocks,
for which government fiscal or monetary policy can mitigate the length or
severity of the recession. A supply shock as contemplated herein may be
unprecedented. The closest example may be recession following the 1973-1974
Arab Oil Embargo. In that case, however, oil was available in the United
States, but not in sufficient supply to meet demand. The dust bowl in the 1930s
resulted in a lack of arable land in the Midwest, which led to the largest
population migration in the United States.138 In the Poe Lock closure scenario,
there is no plan, policy, or remedy that could restart automobile production.
Government policy would be generally limited to transfer payments to those
individuals directly impacted by the event.<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt;">
<span style="font-family: Arial, Helvetica, sans-serif;">Moving iron ore from the mines to the mills is not a viable mitigation;
as one industry executive put it, “it's not even in the realm of the possible;
it's just not going to happen.” Even if the steel mills could accept iron ore
from rail transportation, congested rail lines and the lack of equipment would
make the use of rail impractical. For 160 years, the steel mills along the
Great Lakes have received their iron ore via Lake Carrier; the mills are
designed to receive iron ore by water and there is logistically no way to
receive iron ore by rail. The Great Lakes steel mills are built with the iron
ore inventory facing the water and the rail lines on the other side of the
mills inland for truck or rail shipment of steel out.<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt;">
<span style="font-family: Arial, Helvetica, sans-serif;">There are not enough trucks, or drivers, in the Nation to move the iron
ore from the mines to the mills. Each One Thousand Footer Lake Carrier carries
approximately 70,000 tons of iron ore, which is equivalent to about 3,000
trucks. The mills use the 70,000 tons about every five days, which means that
600 trucks per day--1 truck every 2.4 minutes--would have to enter a steel
mill, drop its load and leave. To bring trucks to 7 mills would mean that, for
every point on the Interstate Highway System between Minnesota and Indiana,
there would be a truck loaded with iron ore passing every 20 seconds on one
side of the road and one truck returning empty on the other side of the road.
The Interstate Highway System would have to be shut down to all traffic except
for the iron ore trucks and no road maintenance could occur. Finally,
OCIA-NISAC estimates that the cost of moving iron ore by truck is approximately
four times the value of the iron ore itself and would likely be
cost-prohibitive in addition to impractical.<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt;">
<span style="font-family: Arial, Helvetica, sans-serif;">In terms of an impact to the North American economy, it is hard to
conceive of a single asset more consequential than the Poe Lock. As outlined in
the report, 10.9 million jobs in the United States, and possibly upwards of 13 million
jobs in North America, are likely dependent on the functioning of the Poe Lock.
An unprecedented supply shock could affect North America if the closure
scenario were to occur. The United States has historical knowledge of how to
respond to shocks caused by financial crises, oil prices or availability, or
falling aggregate demand. There is no similar guide for responding to a supply
shock that incapacitates a large set of industries.<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt;">
<span style="font-family: Arial, Helvetica, sans-serif;">As documented in this report, the iron mining - integrated steel production
- manufacturing, particularly </span><span style="font-family: Arial, Helvetica, sans-serif;">automobile manufacturing, supply chain, is not only consequential, but
potentially one of the least resilient supply chain in North America. The
relationship between the steel mills and the auto assembly plants is complex.
There is a different steel coil for just about every part of an automobile made
with steel, and collectively, there are reportedly some 1500 different recipes
of steel for the automotive industry. Without the steady stream of iron ore
coming from Lake Superior through the Poe Lock, many or all of these 1500
different steel recipes cannot be made. The inability to make just one recipe
could stop production of a particular automobile; the inability to make a
couple of recipes could stop production for a particular automotive company;
and the inability to make a few recipes could stop production of all North
American automotive production."</span></div>
<div class="MsoNormal" style="margin-bottom: 0.0001pt;">
<o:p></o:p></div>
Laurie Thomashttp://www.blogger.com/profile/16611719448125721800noreply@blogger.com0tag:blogger.com,1999:blog-1555376450970352963.post-25632408014876062512016-03-01T12:18:00.000-08:002016-03-01T12:18:16.658-08:00Summary of Coast Guard Office of Port and Facility Compliance (CG-FAC) 2015 Annual Report<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">On March 1, 2016, the Coast Guard Office of Port and Facility
Compliance (CG-FAC) issued the 2015 Annual Report. It can be found at http://www.uscg.mil/hq/cg5/cg544/docs/CG-FAC%20Year%20In%20Review%202015_Final.pdf.
The MTSA community, especially Facility Security Officers, should read the <i>entire report</i>. Important points are
summarized below, using portions of the report. <o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">FSOs should pay particular attention to 2015 MTSA Facility
Enforcement Actions and What’s Coming in 2016.<b><o:p></o:p></b></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<b><span style="font-family: Arial, Helvetica, sans-serif;">Strategy for the
Waterside Security of Especially Hazardous Cargo<o:p></o:p></span></b></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">On 1 September 2015, the Commandant of the Coast Guard
signed the "Strategy for the Waterside Security of Especially Hazardous
Cargo." It seeks to manage the risk
of an attack on the Maritime Transportation System (MTS) involving EHC by
mitigating the Threat, Vulnerability, and Consequence elements of risk through
the Awareness, Prevention, Protection, Response, and Recovery components of the
security spectrum. Security governance to facilitate and improve communication
between industry and government on incident response/recovery, as well as
maritime transportation infrastructure security, will be incorporated through
an Implementation Plan. CG-FAC is
working an initial action plan with a 5 year execution.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<b><span style="font-family: Arial, Helvetica, sans-serif;">Technology<o:p></o:p></span></b></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">USCG is deploying IPads to inspection corps who requested to
be part of the program. This dramatically reduces large quantities of
references and materials that inspectors need to carry around. Other devices
which FAC recommends purchasing, at the unit’s expense, are a Bluetooth
keyboard, portable Bluetooth printer, and Apps. The USCG would appreciate any
feedback and recommendation for use of the iPads provided to the CG- Portal
site. <a href="https://cg.portal.uscg.mil/units/cgfac2/iPads/SitePages/Home.aspx">https://cg.portal.uscg.mil/units/cgfac2/iPads/SitePages/Home.aspx</a>.
<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<b><span style="font-family: Arial, Helvetica, sans-serif;">Port Security
Specialist Program<o:p></o:p></span></b></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">The USCG has conducted a performance planning front end
analysis (FEA) to determine Port Security Specialist and Security Specialist
(Port / Recovery) performance requirements. Ten recommendations were identified
during the FEA. Recommendations from this analysis will help optimize limited
training resources and improve Port Security Specialist and Security Specialist
(Port / Recovery) performance. A 2015 ALCOAST was issued providing an update to
the PSS Program, defining roles and responsibilities of the PSS, and
highlighting accomplishments.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<b><span style="font-family: Arial, Helvetica, sans-serif;">Cybersecurity
Assessment and Risk Management Approach (CARMA) Assessment in Philadelphia<o:p></o:p></span></b></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">During the week of June 8th, DHS Office of Sector Engagement
Critical Infrastructure Resilience, in conjunction with the Coast Guard, led a
cyber risk assessment in the Port of Philadelphia. Agencies involved were DHS, National
Institute of Standards and Technology (NIST), Federal Energy Regulatory Commission
(FERC), Customs and Border Protection (CBP), Transportation Security
Administration (TSA), USCG Sector Del Bay, LANTAREA, CG-FAC, CG-CVC.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<b><span style="font-family: Arial, Helvetica, sans-serif;">Coast Guard LNG
Workgroup<o:p></o:p></span></b></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">Both Harvey-Gulf and TOTE have delivered vessels with LNG
fueled engines, and the LNG workgroup worked closely with field units to
interpret regulations and develop implementation strategies for these new
facilities. CG-FAC chairs the LNG Workgroup, and during 2015 the work group
facilitated the development and release of OES Policy letters 01-15 and 02-15
to, among other things, address gaps in 33 CFR 127 for LNG facilities that will
bunker LNG. The report gives a link for USCG units to access the LNG Workgroup
site in CG Portal (USCG restricted).<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<b><span style="font-family: Arial, Helvetica, sans-serif;">Alternative Security
Program (ASP)<o:p></o:p></span></b></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">There are close to 200 facilities operating under ASPs and
thousands of vessels, more than are using vessel-specific security plans. Since
cyber-security is a topic of growing interest to the entire maritime industry
the Coast Guard is exploring options for how to best incorporate cyber risks
into security plans required by the Maritime Transportation Security Act. During
the past year, two ASP Sponsoring Organization’s Workshops were held in
Washington, DC. These workshops are a great forum for information sharing and
discussions of best practices for both facilities and vessels. The workshop,
held on November 18, 2015, provided an opportunity for in-depth discussions on
cyber risks. Many industry groups are developing cyber security best practices
and the Alternative Security Program potentially provides an ideal way of
addressing cyber risks.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<b><span style="font-family: Arial, Helvetica, sans-serif;">Cyber Risk Management<o:p></o:p></span></b></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">On 15 January 2015, CG-FAC held a public meeting to solicit
input on a policy development project to address cyber security risks in the
marine transportation system. In June 2015, the Commandant announced the
promulgation of the Coast Guard’s first Cyber Strategy. This Strategy presents
a ten-year vision for Coast Guard operations in cyberspace, and lays out our
Service’s highest strategic objectives in this rap- idly evolving operational
domain.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">With the signing of the Cyber Strategy, CG-FAC became the
lead office for implementing the Protect Infrastructure portion of the
Strategy. The newly formed Protect Infrastructure Cyber Strategy Implementation
Team (CSIT) had representatives from nearly every office within CG-5P and also
representatives from other offices including CG-2, CG-6, and CG- 5R. Other
offices outside of HQ have also pitched in, including National Maritime Center
(NMC), Areas and Districts. The CSIT recently submitted an implementation plan
and continues to work to complete identified initiatives. CG-FAC members were
active in supporting Coast Guard wide research and development related to cyber
risks in the marine transportation system.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<b><span style="font-family: Arial, Helvetica, sans-serif;">Cyber Lexicon<o:p></o:p></span></b></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">CG-FAC, working within the Transportation System Sec- tor
Cyber Security Working Group, assisted in developing a Common Cyber Language
for the Transportation Sector. The language can be used to assist sub-sectors
such as airlines or rail within the Transportation Sector have a common language
when discussing cyber issues<span style="background: yellow; mso-highlight: yellow;">.</span>
The trail to this file in Homeport is Missions>Cybersecurity>Cyber
Information> Transportation Sector Common Cyber Language.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<b><span style="font-family: Arial, Helvetica, sans-serif;">Cybersecurity
Assessment and Risk Management Approach (CARMA)<o:p></o:p></span></b></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">CARMA is a DHS developed tool that attempts to identify
cyber risks within the port. It is a stakeholder-vetted list of the Port’s
cyber infrastructure, as defined by its critical functions, supporting value
chains, and specific types of cyber systems. What is important is that it
utilizes local stakeholders to derive a port-level understanding of shared
vulnerabilities and with it a prioritized list of strategies for managing the
identified risks. This allows individual owners and operators to prioritize
budget and resource allocations according to common risks. It also uses the
identified cybersecurity risks to help build valid scenarios that could be
leveraged for sector or national-level cyber exercises. Information on CARMA is
accessed via email at <a href="mailto:ncsd_cipcs@hq.dhs.gov">ncsd_cipcs@hq.dhs.gov</a>.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<b><span style="font-family: Arial, Helvetica, sans-serif;">Cyber Risk Awareness
and Policy Development<o:p></o:p></span></b></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">In 2015, the Coast Guard worked with the National Maritime
Security Advisory Council, the National Offshore Safety Advisory Council, and
many individual industry associations to share cyber information. <o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">In June, the U.S. Coast Guard submitted a paper and
introduced cyber risk management as a topic at the International Maritime
Organization. Transport Canada has been a particularly strong partner in cyber.
CG-FAC sent out 12 cyber related notices in 2015. A new resource section was
also added to Homeport that shares over 100 different links to cyber related
sites from advisories to alerts, assessment tools, recovery resources,
supporting documents, tools, and training and education.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<b><span style="font-family: Arial, Helvetica, sans-serif;">2015 Facility
Inspections Program Statistics<o:p></o:p></span></b></div>
<table border="0" cellpadding="0" cellspacing="0" class="MsoNormalTable" style="border-collapse: collapse; margin-left: 73.15pt; mso-padding-alt: 0in 0in 0in 0in; mso-table-layout-alt: fixed; mso-yfti-tbllook: 480; width: 544px;">
<tbody>
<tr style="height: 20.1pt; mso-height-rule: exactly; mso-yfti-firstrow: yes; mso-yfti-irow: 0;">
<td style="background: red; height: 20.1pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 327.2pt;" valign="top" width="436">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 1.75pt; margin-right: 0in; margin-top: 3.2pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><span style="font-size: 14pt; letter-spacing: -0.3pt;">Total </span></b><b><span style="font-size: 14pt;">regulated<span style="letter-spacing: -.3pt;"> </span>facilities:</span></b><span style="font-size: 14pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 20.1pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 81.15pt;" valign="top" width="108">
<div align="right" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 0in; margin-right: 1.65pt; margin-top: 3.2pt; text-align: right;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><span style="font-size: 14pt; letter-spacing: -0.2pt;">8,211</span></b><span style="font-size: 14pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 16.1pt; mso-height-rule: exactly; mso-yfti-irow: 1;">
<td style="background: red; height: 16.1pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 327.2pt;" valign="top" width="436">
<div class="TableParagraph" style="line-height: 15.4pt; margin-left: 19.75pt; mso-line-height-rule: exactly;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><i><span style="font-size: 14pt;">MTSA-regulated<span style="letter-spacing: -.6pt;"> </span>facilities:</span></i></b><span style="font-size: 14pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 16.1pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 81.15pt;" valign="top" width="108">
<div align="right" class="TableParagraph" style="line-height: 15.4pt; margin-right: 4.35pt; mso-line-height-rule: exactly; text-align: right;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><i><span style="font-size: 14pt;">3,476</span></i></b><span style="font-size: 14pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 16.15pt; mso-height-rule: exactly; mso-yfti-irow: 2;">
<td style="height: 16.15pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 327.2pt;" valign="top" width="436">
<div class="TableParagraph" style="line-height: 15.3pt; margin-left: 1.75pt; mso-line-height-rule: exactly;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><span style="font-size: 14pt; letter-spacing: -0.3pt;">Total </span></b><b><span style="font-size: 14pt;">facility inspections<span style="letter-spacing: -.2pt;"> </span>completed:</span></b><span style="font-size: 14pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 16.15pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 81.15pt;" valign="top" width="108">
<div align="right" class="TableParagraph" style="line-height: 15.3pt; margin-right: 5.15pt; mso-line-height-rule: exactly; text-align: right;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><span style="font-size: 14pt; letter-spacing: -0.15pt;">11,856</span></b><span style="font-size: 14pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 16.15pt; mso-height-rule: exactly; mso-yfti-irow: 3;">
<td style="height: 16.15pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 327.2pt;" valign="top" width="436">
<div class="TableParagraph" style="line-height: 15.45pt; margin-left: 19.75pt; mso-line-height-rule: exactly;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><i><span style="font-size: 14pt;">MTSA facility inspections<span style="letter-spacing: -1.7pt;"> </span>completed:</span></i></b><span style="font-size: 14pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 16.15pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 81.15pt;" valign="top" width="108">
<div align="right" class="TableParagraph" style="line-height: 15.45pt; margin-right: 7.85pt; mso-line-height-rule: exactly; text-align: right;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><i><span style="font-size: 14pt;">5,937</span></i></b><span style="font-size: 14pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 16.0pt; mso-height-rule: exactly; mso-yfti-irow: 4;">
<td style="height: 16.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 327.2pt;" valign="top" width="436">
<div class="TableParagraph" style="line-height: 15.3pt; margin-left: 1.75pt; mso-line-height-rule: exactly;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><span style="font-size: 14pt; letter-spacing: -0.3pt;">Total </span></b><b><span style="font-size: 14pt;">container inspections<span style="letter-spacing: -.4pt;"> </span>completed:</span></b><span style="font-size: 14pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 16.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 81.15pt;" valign="top" width="108">
<div align="right" class="TableParagraph" style="line-height: 15.3pt; margin-right: 7.9pt; mso-line-height-rule: exactly; text-align: right;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><span style="font-size: 14pt; letter-spacing: -0.05pt;">18,053</span></b><span style="font-size: 14pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 16.1pt; mso-height-rule: exactly; mso-yfti-irow: 5;">
<td style="height: 16.1pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 327.2pt;" valign="top" width="436">
<div class="TableParagraph" style="line-height: 15.35pt; margin-left: 1.75pt; mso-line-height-rule: exactly;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><span style="font-size: 14pt; letter-spacing: -0.3pt;">Total </span></b><b><span style="font-size: 14pt;">transfer monitors<span style="letter-spacing: -.2pt;"> </span>conducted:</span></b><span style="font-size: 14pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 16.1pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 81.15pt;" valign="top" width="108">
<div align="right" class="TableParagraph" style="line-height: 15.35pt; margin-right: 7.8pt; mso-line-height-rule: exactly; text-align: right;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><span style="font-size: 14pt;">456</span></b><span style="font-size: 14pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 16.15pt; mso-height-rule: exactly; mso-yfti-irow: 6;">
<td style="height: 16.15pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 327.2pt;" valign="top" width="436">
<div class="TableParagraph" style="line-height: 15.35pt; margin-left: 1.75pt; mso-line-height-rule: exactly;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><span style="font-size: 14pt; letter-spacing: -0.3pt;">Total </span></b><b><span style="font-size: 14pt;">operational controls (COTP<span style="letter-spacing: -1.3pt;"> </span>Orders)</span></b><span style="font-size: 14pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 16.15pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 81.15pt;" valign="top" width="108">
<div align="right" class="TableParagraph" style="line-height: 15.35pt; margin-right: 7.9pt; mso-line-height-rule: exactly; text-align: right;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><span style="font-size: 14pt;">34</span></b><span style="font-size: 14pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 16.15pt; mso-height-rule: exactly; mso-yfti-irow: 7;">
<td style="height: 16.15pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 327.2pt;" valign="top" width="436">
<div class="TableParagraph" style="line-height: 15.4pt; margin-left: 19.75pt; mso-line-height-rule: exactly;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><i><span style="font-size: 14pt;">Security COTP<span style="letter-spacing: -.9pt;"> </span>Orders</span></i></b><span style="font-size: 14pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 16.15pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 81.15pt;" valign="top" width="108">
<div align="right" class="TableParagraph" style="line-height: 15.4pt; margin-right: 7.9pt; mso-line-height-rule: exactly; text-align: right;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><i><span style="font-size: 14pt;">16</span></i></b><span style="font-size: 14pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 20.05pt; mso-height-rule: exactly; mso-yfti-irow: 8;">
<td style="height: 20.05pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 327.2pt;" valign="top" width="436">
<div class="TableParagraph" style="line-height: 15.35pt; margin-left: 19.75pt; mso-line-height-rule: exactly;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><i><span style="font-size: 14pt;">Safety/Environmental Protection COTP<span style="letter-spacing: -1.7pt;"> </span>Orders</span></i></b><span style="font-size: 14pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 20.05pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 81.15pt;" valign="top" width="108">
<div align="right" class="TableParagraph" style="line-height: 15.35pt; margin-right: 7.9pt; mso-line-height-rule: exactly; text-align: right;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><i><span style="font-size: 14pt;">19</span></i></b><span style="font-size: 14pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 20.05pt; mso-height-rule: exactly; mso-yfti-irow: 9; mso-yfti-lastrow: yes;">
<td style="height: 20.05pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 327.2pt;" valign="top" width="436">
<div class="TableParagraph" style="line-height: 15.35pt; margin-left: 19.75pt; mso-line-height-rule: exactly;">
<br /></div>
<div class="TableParagraph" style="line-height: 15.35pt; margin-left: 19.75pt; mso-line-height-rule: exactly; text-indent: -92.9pt;">
<br /></div>
</td>
<td style="height: 20.05pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 81.15pt;" valign="top" width="108">
<div align="right" class="TableParagraph" style="line-height: 15.35pt; margin-right: 7.9pt; mso-line-height-rule: exactly; text-align: right;">
<br /></div>
</td>
</tr>
</tbody></table>
<div class="MsoNormal">
<b><span style="font-family: Arial, Helvetica, sans-serif;">2015 MTSA Security
Compliance by District<o:p></o:p></span></b></div>
<table border="0" cellpadding="0" cellspacing="0" class="MsoNormalTable" style="border-collapse: collapse; margin-left: 100.5pt; mso-padding-alt: 0in 0in 0in 0in; mso-table-layout-alt: fixed; mso-yfti-tbllook: 480;">
<tbody>
<tr style="height: 20.3pt; mso-height-rule: exactly; mso-yfti-firstrow: yes; mso-yfti-irow: 0;">
<td style="background: red; height: 20.3pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 88.6pt;" valign="top" width="118">
<div class="TableParagraph" style="line-height: 12.25pt; margin-left: 10.0pt; mso-line-height-rule: exactly;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><span style="font-size: 12pt;">District</span></b><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 20.3pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 97.45pt;" valign="top" width="130">
<div align="right" class="TableParagraph" style="line-height: 12.25pt; margin-right: 25.45pt; mso-line-height-rule: exactly; text-align: right;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><span style="font-size: 12pt; letter-spacing: -0.05pt;">FSPs*</span></b><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 20.3pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 141.55pt;" valign="top" width="189">
<div align="center" class="TableParagraph" style="line-height: 12.25pt; margin-left: 5.2pt; mso-line-height-rule: exactly; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><span style="font-size: 12pt;">MTSA<span style="letter-spacing: -.2pt;"> </span>Inspections</span></b><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 20.3pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 90.95pt;" valign="top" width="121">
<div align="center" class="TableParagraph" style="line-height: 12.25pt; margin-left: 10.3pt; mso-line-height-rule: exactly; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><span style="font-size: 12pt;">Deficiencies</span></b><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 29.45pt; mso-height-rule: exactly; mso-yfti-irow: 1;">
<td style="background: red; height: 29.45pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 88.6pt;" valign="top" width="118">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 22.0pt; margin-right: 0in; margin-top: 6.95pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><span style="font-size: 12pt;">1st</span></b><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 29.45pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 97.45pt;" valign="top" width="130">
<div align="right" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 0in; margin-right: .45in; margin-top: 6.7pt; text-align: right;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">298</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 29.45pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 141.55pt;" valign="top" width="189">
<div align="center" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.1pt; margin-right: 0in; margin-top: 6.7pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">949</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 29.45pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 90.95pt;" valign="top" width="121">
<div align="center" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 10.2pt; margin-right: 0in; margin-top: 6.7pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">164</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 30.15pt; mso-height-rule: exactly; mso-yfti-irow: 2;">
<td style="background: red; height: 30.15pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 88.6pt;" valign="top" width="118">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 20.9pt; margin-right: 0in; margin-top: 7.65pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><span style="font-size: 12pt;">5th</span></b><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 30.15pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 97.45pt;" valign="top" width="130">
<div align="right" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 0in; margin-right: .45in; margin-top: 7.4pt; text-align: right;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">166</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 30.15pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 141.55pt;" valign="top" width="189">
<div align="center" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.1pt; margin-right: 0in; margin-top: 7.4pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">451</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 30.15pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 90.95pt;" valign="top" width="121">
<div align="center" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 10.2pt; margin-right: 0in; margin-top: 7.4pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">129</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 30.1pt; mso-height-rule: exactly; mso-yfti-irow: 3;">
<td style="background: red; height: 30.1pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 88.6pt;" valign="top" width="118">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 20.9pt; margin-right: 0in; margin-top: 7.6pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><span style="font-size: 12pt;">7th</span></b><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 30.1pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 97.45pt;" valign="top" width="130">
<div align="right" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 0in; margin-right: .45in; margin-top: 7.4pt; text-align: right;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">310</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 30.1pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 141.55pt;" valign="top" width="189">
<div align="center" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.1pt; margin-right: 0in; margin-top: 7.4pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">928</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 30.1pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 90.95pt;" valign="top" width="121">
<div align="center" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 10.2pt; margin-right: 0in; margin-top: 7.4pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">241</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 30.05pt; mso-height-rule: exactly; mso-yfti-irow: 4;">
<td style="background: red; height: 30.05pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 88.6pt;" valign="top" width="118">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 20.9pt; margin-right: 0in; margin-top: 7.6pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><span style="font-size: 12pt;">8th</span></b><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 30.05pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 97.45pt;" valign="top" width="130">
<div align="right" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 0in; margin-right: .45in; margin-top: 7.4pt; text-align: right;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">905</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 30.05pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 141.55pt;" valign="top" width="189">
<div align="center" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.1pt; margin-right: 0in; margin-top: 7.4pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">1902</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 30.05pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 90.95pt;" valign="top" width="121">
<div align="center" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 10.2pt; margin-right: 0in; margin-top: 7.4pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">570</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 30.05pt; mso-height-rule: exactly; mso-yfti-irow: 5;">
<td style="background: red; height: 30.05pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 88.6pt;" valign="top" width="118">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 20.9pt; margin-right: 0in; margin-top: 7.55pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><span style="font-size: 12pt;">9th</span></b><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 30.05pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 97.45pt;" valign="top" width="130">
<div align="right" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 0in; margin-right: .45in; margin-top: 7.3pt; text-align: right;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">304</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 30.05pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 141.55pt;" valign="top" width="189">
<div align="center" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.1pt; margin-right: 0in; margin-top: 7.3pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">691</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 30.05pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 90.95pt;" valign="top" width="121">
<div align="center" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 10.2pt; margin-right: 0in; margin-top: 7.3pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">120</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 30.1pt; mso-height-rule: exactly; mso-yfti-irow: 6;">
<td style="background: red; height: 30.1pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 88.6pt;" valign="top" width="118">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 17.9pt; margin-right: 0in; margin-top: 7.6pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><span style="font-size: 12pt;">11th</span></b><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 30.1pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 97.45pt;" valign="top" width="130">
<div align="right" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 0in; margin-right: .45in; margin-top: 7.4pt; text-align: right;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">135</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 30.1pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 141.55pt;" valign="top" width="189">
<div align="center" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.1pt; margin-right: 0in; margin-top: 7.4pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">326</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 30.1pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 90.95pt;" valign="top" width="121">
<div align="center" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 10.2pt; margin-right: 0in; margin-top: 7.4pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">120</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 30.15pt; mso-height-rule: exactly; mso-yfti-irow: 7;">
<td style="background: red; height: 30.15pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 88.6pt;" valign="top" width="118">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 17.9pt; margin-right: 0in; margin-top: 7.6pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><span style="font-size: 12pt;">13th</span></b><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 30.15pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 97.45pt;" valign="top" width="130">
<div align="right" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 0in; margin-right: .45in; margin-top: 7.4pt; text-align: right;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">139</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 30.15pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 141.55pt;" valign="top" width="189">
<div align="center" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.1pt; margin-right: 0in; margin-top: 7.4pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">257</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 30.15pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 90.95pt;" valign="top" width="121">
<div align="center" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 10.2pt; margin-right: 0in; margin-top: 7.4pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">106</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 30.05pt; mso-height-rule: exactly; mso-yfti-irow: 8;">
<td style="height: 30.05pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 88.6pt;" valign="top" width="118">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 17.9pt; margin-right: 0in; margin-top: 7.65pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><span style="font-size: 12pt;">14th</span></b><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 30.05pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 97.45pt;" valign="top" width="130">
<div align="center" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 14.45pt; margin-right: 0in; margin-top: 7.4pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">77</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 30.05pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 141.55pt;" valign="top" width="189">
<div align="center" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.1pt; margin-right: 0in; margin-top: 7.4pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">214</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 30.05pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 90.95pt;" valign="top" width="121">
<div align="center" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 10.2pt; margin-right: 0in; margin-top: 7.4pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">142</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 30.2pt; mso-height-rule: exactly; mso-yfti-irow: 9;">
<td style="height: 30.2pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 88.6pt;" valign="top" width="118">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 17.9pt; margin-right: 0in; margin-top: 7.55pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><span style="font-size: 12pt;">17th</span></b><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 30.2pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 97.45pt;" valign="top" width="130">
<div align="center" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 14.45pt; margin-right: 0in; margin-top: 7.3pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">98</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 30.2pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 141.55pt;" valign="top" width="189">
<div align="center" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.1pt; margin-right: 0in; margin-top: 7.3pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">219</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 30.2pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 90.95pt;" valign="top" width="121">
<div align="center" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 10.2pt; margin-right: 0in; margin-top: 7.3pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">27</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 21.05pt; mso-height-rule: exactly; mso-yfti-irow: 10; mso-yfti-lastrow: yes;">
<td style="height: 21.05pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 88.6pt;" valign="top" width="118">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 15.6pt; margin-right: 0in; margin-top: 7.5pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><span style="font-size: 12pt;">Total</span></b><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 21.05pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 97.45pt;" valign="top" width="130">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 43.95pt; margin-right: 0in; margin-top: 7.5pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><span style="font-size: 12pt;">2432</span></b><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 21.05pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 141.55pt;" valign="top" width="189">
<div align="center" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.1pt; margin-right: 0in; margin-top: 7.5pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><span style="font-size: 12pt;">5937</span></b><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="height: 21.05pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 90.95pt;" valign="top" width="121">
<div align="center" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 10.2pt; margin-right: 0in; margin-top: 7.5pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><span style="font-size: 12pt;">1619</span></b><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
</tr>
</tbody></table>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
<b><span style="font-family: Arial, Helvetica, sans-serif;">Container Update<o:p></o:p></span></b></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">CG-FAC continuously seeks to improve the National Container
Inspection Program (NCIP) guidance and streamline the process for both industry
and the field. CG-FAC recently met with Hapag-Lloyd and the National Cargo
Bureau to discuss industry and Coast Guard concerns and issues with the
shipment of containers in an effort to identify ways to mitigate risks. Hapag-Lloyd
has developed a system called “Watchdog”, that analyzes shipping documents
searching for key words to assist in selecting containers for inspection.
Watchdog has enabled Hapag-Lloyd to inspect 20% of all containers shipped by
the company. <o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">Mis-declared cargo and leakage are the most prominent issues
ailing the shipment of containers and account for 86% of deficiencies according
to the Cargo Incident Notification System website. According to the same
website, over 70% of those deficiencies involve general cargo shipments, which
point to the success of inspection programs focused on declared Hazardous
Materials (HAZMAT).<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">Higher national compliance rates in declared HAZMAT shipments
led to a shift for inspections rates of declared HAZMAT and general cargo
container shipments. Previous guidance prioritized HAZMAT over general cargo shipments
at a 90% to 10% inspection goal respectively. On average, of the total
containers inspected nationally the Coast Guard has achieved roughly 60% to 40%
HAZMAT to general cargo annually.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<b><span style="font-family: Arial, Helvetica, sans-serif;">Transportation Worker
Identification Credential (TWIC) Verifications<o:p></o:p></span></b></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">As part of the MTSA security program, Facility Inspectors
conducted a combined 48,289 visual and electronic inspections of TWIC cards in
2015, and identified 970 instances of non-compliance with TWIC
requirements. CG-FAC is currently
conducting market research for replacement readers; current hand-helds are
reaching the end of their service life. There are currently a few USCG units conducting
field testing for iPad based reader applications. <o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">USCG TWIC Implementation branch members worked directly with
counterparts at TSA to discuss and address TWIC program improvements and
issues. TSA has recently begun implementation of a civil enforcement program
for individual TWIC holders violating regulatory requirements. Many
Transportation Security Inspectors – Surface (TSI-S) personnel have reached out
to Districts and Sectors to coordinate implementation of this inspection
program.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<b><span style="font-family: Arial, Helvetica, sans-serif;">2015 MTSA Facility
Enforcement Actions<o:p></o:p></span></b></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">In 2015, the Coast Guard completed 4,717 security-related
MTSA annual and spot check ex- aminations and recorded 131 enforcement
activities against MTSA-regulated facility owners or operators for
noncompliance with MTSA regulations. The
131 enforcement activities executed in 2015 took place at 115 MTSA-regulated
facilities and included official letters of warning or administrative civil
penalties.<o:p></o:p></span></div>
<table border="0" cellpadding="0" cellspacing="0" class="MsoNormalTable" style="border-collapse: collapse; margin-left: 5.0pt; mso-padding-alt: 0in 0in 0in 0in; mso-table-layout-alt: fixed; mso-yfti-tbllook: 480;">
<tbody>
<tr style="height: 42.4pt; mso-height-rule: exactly; mso-yfti-firstrow: yes; mso-yfti-irow: 0;">
<td style="background: #BEBEBE; border: solid black 1.0pt; height: 42.4pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 104.1pt;" valign="top" width="139">
<div class="TableParagraph">
<br /></div>
<div class="TableParagraph" style="margin-top: .4pt;">
<br /></div>
<div class="TableParagraph" style="margin-left: 30.35pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><span style="font-size: 12pt;">Citation</span></b><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="background: #BEBEBE; border-left: none; border: solid black 1.0pt; height: 42.4pt; mso-border-left-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 272.05pt;" valign="top" width="363">
<div class="TableParagraph">
<br /></div>
<div class="TableParagraph" style="margin-top: .4pt;">
<br /></div>
<div align="center" class="TableParagraph" style="margin-right: .05pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><span style="font-size: 12pt;">Citation<span style="letter-spacing: -.1pt;"> </span>Title</span></b><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="background: #BEBEBE; border-left: none; border: solid black 1.0pt; height: 42.4pt; mso-border-left-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 90.8pt;" valign="top" width="121">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 20.8pt; margin-right: 11.6pt; margin-top: 0in; text-indent: -9.25pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><span style="font-size: 12pt; letter-spacing: -0.05pt;">Enforcement</span></b><b><span style="font-size: 12pt;"> Activities Executed</span></b><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 22.35pt; mso-height-rule: exactly; mso-yfti-irow: 1;">
<td style="background: red; border-top: none; border: solid black 1.0pt; height: 22.35pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 104.1pt;" valign="top" width="139">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.3pt; margin-right: 0in; margin-top: .1in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">33 CFR<span style="letter-spacing: -.1pt;"> </span>101.305</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="border-bottom: solid black 1.0pt; border-left: none; border-right: solid black 1.0pt; border-top: none; height: 22.35pt; mso-border-left-alt: solid black 1.0pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 272.05pt;" valign="top" width="363">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.25pt; margin-right: 0in; margin-top: .1in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">Reporting, Breach of<span style="letter-spacing: -.15pt;"> </span>Security</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="border-bottom: solid black 1.0pt; border-left: none; border-right: solid black 1.0pt; border-top: none; height: 22.35pt; mso-border-left-alt: solid black 1.0pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 90.8pt;" valign="top" width="121">
<div align="center" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 0in; margin-right: .05pt; margin-top: 3.35pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">3</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 22.35pt; mso-height-rule: exactly; mso-yfti-irow: 2;">
<td style="background: red; border-top: none; border: solid black 1.0pt; height: 22.35pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 104.1pt;" valign="top" width="139">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.3pt; margin-right: 0in; margin-top: .1in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">33 CFR<span style="letter-spacing: -.1pt;"> </span>105.125</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="border-bottom: solid black 1.0pt; border-left: none; border-right: solid black 1.0pt; border-top: none; height: 22.35pt; mso-border-left-alt: solid black 1.0pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 272.05pt;" valign="top" width="363">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.25pt; margin-right: 0in; margin-top: .1in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">Noncompliance</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="border-bottom: solid black 1.0pt; border-left: none; border-right: solid black 1.0pt; border-top: none; height: 22.35pt; mso-border-left-alt: solid black 1.0pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 90.8pt;" valign="top" width="121">
<div align="center" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 0in; margin-right: .05pt; margin-top: 3.35pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">3</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 22.3pt; mso-height-rule: exactly; mso-yfti-irow: 3;">
<td style="background: red; border-top: none; border: solid black 1.0pt; height: 22.3pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 104.1pt;" valign="top" width="139">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.3pt; margin-right: 0in; margin-top: .1in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">33 CFR<span style="letter-spacing: -.1pt;"> </span>105.140</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="border-bottom: solid black 1.0pt; border-left: none; border-right: solid black 1.0pt; border-top: none; height: 22.3pt; mso-border-left-alt: solid black 1.0pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 272.05pt;" valign="top" width="363">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.25pt; margin-right: 0in; margin-top: .1in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">Alternative Security<span style="letter-spacing: -.45pt;"> </span>Program</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="border-bottom: solid black 1.0pt; border-left: none; border-right: solid black 1.0pt; border-top: none; height: 22.3pt; mso-border-left-alt: solid black 1.0pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 90.8pt;" valign="top" width="121">
<div align="center" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 0in; margin-right: .05pt; margin-top: 3.35pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">1</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 22.35pt; mso-height-rule: exactly; mso-yfti-irow: 4;">
<td style="background: red; border-top: none; border: solid black 1.0pt; height: 22.35pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 104.1pt;" valign="top" width="139">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.3pt; margin-right: 0in; margin-top: .1in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">33 CFR<span style="letter-spacing: -.1pt;"> </span>105.200</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="border-bottom: solid black 1.0pt; border-left: none; border-right: solid black 1.0pt; border-top: none; height: 22.35pt; mso-border-left-alt: solid black 1.0pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 272.05pt;" valign="top" width="363">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.25pt; margin-right: 0in; margin-top: .1in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">Owner or operator<span style="letter-spacing: -.35pt;"> </span>requirements</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="border-bottom: solid black 1.0pt; border-left: none; border-right: solid black 1.0pt; border-top: none; height: 22.35pt; mso-border-left-alt: solid black 1.0pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 90.8pt;" valign="top" width="121">
<div align="right" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 0in; margin-right: 38.85pt; margin-top: 3.35pt; text-align: right;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">27</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 22.35pt; mso-height-rule: exactly; mso-yfti-irow: 5;">
<td style="background: red; border-top: none; border: solid black 1.0pt; height: 22.35pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 104.1pt;" valign="top" width="139">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.3pt; margin-right: 0in; margin-top: .1in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">33 CFR<span style="letter-spacing: -.1pt;"> </span>105.205</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="border-bottom: solid black 1.0pt; border-left: none; border-right: solid black 1.0pt; border-top: none; height: 22.35pt; mso-border-left-alt: solid black 1.0pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 272.05pt;" valign="top" width="363">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.25pt; margin-right: 0in; margin-top: .1in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">Facility Security Officer<span style="letter-spacing: -.6pt;"> </span>requirements</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="border-bottom: solid black 1.0pt; border-left: none; border-right: solid black 1.0pt; border-top: none; height: 22.35pt; mso-border-left-alt: solid black 1.0pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 90.8pt;" valign="top" width="121">
<div align="center" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 0in; margin-right: .05pt; margin-top: 3.35pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">7</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 22.35pt; mso-height-rule: exactly; mso-yfti-irow: 6;">
<td style="background: red; border-top: none; border: solid black 1.0pt; height: 22.35pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 104.1pt;" valign="top" width="139">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.3pt; margin-right: 0in; margin-top: 7.15pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">33 CFR<span style="letter-spacing: -.1pt;"> </span>105.210</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="border-bottom: solid black 1.0pt; border-left: none; border-right: solid black 1.0pt; border-top: none; height: 22.35pt; mso-border-left-alt: solid black 1.0pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 272.05pt;" valign="top" width="363">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.25pt; margin-right: 0in; margin-top: 7.15pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">Facility personnel with security<span style="letter-spacing: -.5pt;"> </span>duties</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="border-bottom: solid black 1.0pt; border-left: none; border-right: solid black 1.0pt; border-top: none; height: 22.35pt; mso-border-left-alt: solid black 1.0pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 90.8pt;" valign="top" width="121">
<div align="right" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 0in; margin-right: 38.85pt; margin-top: 3.35pt; text-align: right;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">13</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 22.35pt; mso-height-rule: exactly; mso-yfti-irow: 7;">
<td style="background: red; border-top: none; border: solid black 1.0pt; height: 22.35pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 104.1pt;" valign="top" width="139">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.3pt; margin-right: 0in; margin-top: .1in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">33 CFR<span style="letter-spacing: -.1pt;"> </span>105.220</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="border-bottom: solid black 1.0pt; border-left: none; border-right: solid black 1.0pt; border-top: none; height: 22.35pt; mso-border-left-alt: solid black 1.0pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 272.05pt;" valign="top" width="363">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.25pt; margin-right: 0in; margin-top: .1in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">Drill and exercise<span style="letter-spacing: -.3pt;"> </span>requirements</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="border-bottom: solid black 1.0pt; border-left: none; border-right: solid black 1.0pt; border-top: none; height: 22.35pt; mso-border-left-alt: solid black 1.0pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 90.8pt;" valign="top" width="121">
<div align="right" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 0in; margin-right: 38.85pt; margin-top: 3.35pt; text-align: right;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">15</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 22.35pt; mso-height-rule: exactly; mso-yfti-irow: 8;">
<td style="background: red; border-top: none; border: solid black 1.0pt; height: 22.35pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 104.1pt;" valign="top" width="139">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.3pt; margin-right: 0in; margin-top: 7.15pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">33 CFR<span style="letter-spacing: -.1pt;"> </span>105.225</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="border-bottom: solid black 1.0pt; border-left: none; border-right: solid black 1.0pt; border-top: none; height: 22.35pt; mso-border-left-alt: solid black 1.0pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 272.05pt;" valign="top" width="363">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.25pt; margin-right: 0in; margin-top: 7.15pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">Facility recordkeeping<span style="letter-spacing: -.45pt;"> </span>requirements</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="border-bottom: solid black 1.0pt; border-left: none; border-right: solid black 1.0pt; border-top: none; height: 22.35pt; mso-border-left-alt: solid black 1.0pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 90.8pt;" valign="top" width="121">
<div align="center" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 0in; margin-right: .05pt; margin-top: 3.35pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">4</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 22.35pt; mso-height-rule: exactly; mso-yfti-irow: 9;">
<td style="background: red; border-top: none; border: solid black 1.0pt; height: 22.35pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 104.1pt;" valign="top" width="139">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.3pt; margin-right: 0in; margin-top: 7.15pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">33 CFR<span style="letter-spacing: -.1pt;"> </span>105.255</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="border-bottom: solid black 1.0pt; border-left: none; border-right: solid black 1.0pt; border-top: none; height: 22.35pt; mso-border-left-alt: solid black 1.0pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 272.05pt;" valign="top" width="363">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.25pt; margin-right: 0in; margin-top: 7.15pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">Security measures for access<span style="letter-spacing: -.45pt;"> </span>control</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="border-bottom: solid black 1.0pt; border-left: none; border-right: solid black 1.0pt; border-top: none; height: 22.35pt; mso-border-left-alt: solid black 1.0pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 90.8pt;" valign="top" width="121">
<div align="right" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 0in; margin-right: 38.85pt; margin-top: 3.3pt; text-align: right;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">29</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 22.35pt; mso-height-rule: exactly; mso-yfti-irow: 10;">
<td style="background: red; border-top: none; border: solid black 1.0pt; height: 22.35pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 104.1pt;" valign="top" width="139">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.3pt; margin-right: 0in; margin-top: 7.15pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">33 CFR<span style="letter-spacing: -.1pt;"> </span>105.260</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="border-bottom: solid black 1.0pt; border-left: none; border-right: solid black 1.0pt; border-top: none; height: 22.35pt; mso-border-left-alt: solid black 1.0pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 272.05pt;" valign="top" width="363">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.25pt; margin-right: 0in; margin-top: 7.15pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">Security measures for restricted<span style="letter-spacing: -.5pt;"> </span>areas</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="border-bottom: solid black 1.0pt; border-left: none; border-right: solid black 1.0pt; border-top: none; height: 22.35pt; mso-border-left-alt: solid black 1.0pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 90.8pt;" valign="top" width="121">
<div align="center" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 0in; margin-right: .05pt; margin-top: 3.3pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">8</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 22.35pt; mso-height-rule: exactly; mso-yfti-irow: 11;">
<td style="background: red; border-top: none; border: solid black 1.0pt; height: 22.35pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 104.1pt;" valign="top" width="139">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.3pt; margin-right: 0in; margin-top: 7.15pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">33 CFR<span style="letter-spacing: -.1pt;"> </span>105.275</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="border-bottom: solid black 1.0pt; border-left: none; border-right: solid black 1.0pt; border-top: none; height: 22.35pt; mso-border-left-alt: solid black 1.0pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 272.05pt;" valign="top" width="363">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.25pt; margin-right: 0in; margin-top: 7.15pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">Security measures for<span style="letter-spacing: -.35pt;"> </span>monitoring</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="border-bottom: solid black 1.0pt; border-left: none; border-right: solid black 1.0pt; border-top: none; height: 22.35pt; mso-border-left-alt: solid black 1.0pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 90.8pt;" valign="top" width="121">
<div align="center" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 0in; margin-right: .05pt; margin-top: 3.3pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">3</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 22.3pt; mso-height-rule: exactly; mso-yfti-irow: 12;">
<td style="background: red; border-top: none; border: solid black 1.0pt; height: 22.3pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 104.1pt;" valign="top" width="139">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.3pt; margin-right: 0in; margin-top: 7.15pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">33 CFR<span style="letter-spacing: -.1pt;"> </span>105.290</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="border-bottom: solid black 1.0pt; border-left: none; border-right: solid black 1.0pt; border-top: none; height: 22.3pt; mso-border-left-alt: solid black 1.0pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 272.05pt;" valign="top" width="363">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.25pt; margin-right: 0in; margin-top: 7.15pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">Additional cruise ship terminal<span style="letter-spacing: -.45pt;"> </span>requirements</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="border-bottom: solid black 1.0pt; border-left: none; border-right: solid black 1.0pt; border-top: none; height: 22.3pt; mso-border-left-alt: solid black 1.0pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 90.8pt;" valign="top" width="121">
<div align="center" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 0in; margin-right: .05pt; margin-top: 3.3pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">2</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 22.35pt; mso-height-rule: exactly; mso-yfti-irow: 13;">
<td style="background: red; border-top: none; border: solid black 1.0pt; height: 22.35pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 104.1pt;" valign="top" width="139">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.3pt; margin-right: 0in; margin-top: 7.25pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">33 CFR<span style="letter-spacing: -.1pt;"> </span>105.305</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="border-bottom: solid black 1.0pt; border-left: none; border-right: solid black 1.0pt; border-top: none; height: 22.35pt; mso-border-left-alt: solid black 1.0pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 272.05pt;" valign="top" width="363">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.25pt; margin-right: 0in; margin-top: 7.25pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">Requirements for facility security<span style="letter-spacing: -.6pt;"> </span>assessments</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="border-bottom: solid black 1.0pt; border-left: none; border-right: solid black 1.0pt; border-top: none; height: 22.35pt; mso-border-left-alt: solid black 1.0pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 90.8pt;" valign="top" width="121">
<div align="center" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 0in; margin-right: .05pt; margin-top: 3.4pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">1</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 22.35pt; mso-height-rule: exactly; mso-yfti-irow: 14;">
<td style="background: red; border-top: none; border: solid black 1.0pt; height: 22.35pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 104.1pt;" valign="top" width="139">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.3pt; margin-right: 0in; margin-top: 7.25pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">33 CFR<span style="letter-spacing: -.1pt;"> </span>105.400</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="border-bottom: solid black 1.0pt; border-left: none; border-right: solid black 1.0pt; border-top: none; height: 22.35pt; mso-border-left-alt: solid black 1.0pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 272.05pt;" valign="top" width="363">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.25pt; margin-right: 0in; margin-top: 7.25pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">Facility Security<span style="letter-spacing: -.4pt;"> </span>Plans</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="border-bottom: solid black 1.0pt; border-left: none; border-right: solid black 1.0pt; border-top: none; height: 22.35pt; mso-border-left-alt: solid black 1.0pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 90.8pt;" valign="top" width="121">
<div align="center" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 0in; margin-right: .05pt; margin-top: 3.45pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">5</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 22.35pt; mso-height-rule: exactly; mso-yfti-irow: 15;">
<td style="background: red; border-top: none; border: solid black 1.0pt; height: 22.35pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 104.1pt;" valign="top" width="139">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.3pt; margin-right: 0in; margin-top: 7.25pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">33 CFR<span style="letter-spacing: -.1pt;"> </span>105.410</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="border-bottom: solid black 1.0pt; border-left: none; border-right: solid black 1.0pt; border-top: none; height: 22.35pt; mso-border-left-alt: solid black 1.0pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 272.05pt;" valign="top" width="363">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.25pt; margin-right: 0in; margin-top: 7.25pt;">
<span style="font-size: 12pt;"><span style="font-family: Arial, Helvetica, sans-serif;">Facility
Security Plans – Submission and<span style="letter-spacing: -.45pt;"> </span>approval<o:p></o:p></span></span></div>
</td>
<td style="border-bottom: solid black 1.0pt; border-left: none; border-right: solid black 1.0pt; border-top: none; height: 22.35pt; mso-border-left-alt: solid black 1.0pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 90.8pt;" valign="top" width="121">
<div align="center" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 0in; margin-right: .05pt; margin-top: 3.4pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">7</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 22.35pt; mso-height-rule: exactly; mso-yfti-irow: 16;">
<td style="border-top: none; border: solid black 1.0pt; height: 22.35pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 104.1pt;" valign="top" width="139">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.3pt; margin-right: 0in; margin-top: 7.25pt;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">33 CFR<span style="letter-spacing: -.1pt;"> </span>105.415</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="border-bottom: solid black 1.0pt; border-left: none; border-right: solid black 1.0pt; border-top: none; height: 22.35pt; mso-border-left-alt: solid black 1.0pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 272.05pt;" valign="top" width="363">
<div class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 5.25pt; margin-right: 0in; margin-top: 7.25pt;">
<span style="font-size: 12pt;"><span style="font-family: Arial, Helvetica, sans-serif;">Facility
Security Plans – Amendment and<span style="letter-spacing: -.4pt;"> </span>audit<o:p></o:p></span></span></div>
</td>
<td style="border-bottom: solid black 1.0pt; border-left: none; border-right: solid black 1.0pt; border-top: none; height: 22.35pt; mso-border-left-alt: solid black 1.0pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 90.8pt;" valign="top" width="121">
<div align="center" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 0in; margin-right: .05pt; margin-top: 3.4pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><span style="font-size: 12pt;">3</span><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
</tr>
<tr style="height: 21.75pt; mso-height-rule: exactly; mso-yfti-irow: 17; mso-yfti-lastrow: yes;">
<td colspan="2" style="border-top: none; border: solid black 1.0pt; height: 21.75pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 376.1pt;" valign="top" width="501">
<div align="center" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 0in; margin-right: .05pt; margin-top: 7.0pt; text-align: center;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><span style="font-size: 12pt;">Total</span></b><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
<td style="border-bottom: solid black 1.0pt; border-left: none; border-right: solid black 1.0pt; border-top: none; height: 21.75pt; mso-border-left-alt: solid black 1.0pt; mso-border-top-alt: solid black 1.0pt; mso-height-rule: exactly; padding: 0in 0in 0in 0in; width: 90.8pt;" valign="top" width="121">
<div align="right" class="TableParagraph" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: 0in; margin-right: 35.8pt; margin-top: 7.0pt; text-align: right;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b><span style="font-size: 12pt;">131</span></b><span style="font-size: 12pt;"><o:p></o:p></span></span></div>
</td>
</tr>
</tbody></table>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">As noted on the previous page, as in 2014, almost 50% of
Coast Guard enforcement actions at regulated facilities were for 33CFR105.200
and 105.255 violations.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<b><span style="font-family: Arial, Helvetica, sans-serif;">Rulemakings<o:p></o:p></span></b></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">Seafarer’s Access to Maritime Facilities - On July 27, 2015,
the public comment period for the Seafarer’s Access to Maritime Facilities
Notice of Proposed Rulemaking (NPRM) officially closed. The 162 comments have
been adjudicated and the Final Rule is being developed. This proposed rule
would implement section 811 of the Coast Guard Authorization Act of 2010, and
requires each owner or operator of a facility regulated by the Coast Guard to
implement a system that provides seafarers and other individuals with access
between vessels moored at the facility and the facility gate, in a timely
manner and at no cost to the seafarer or other individual.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">Consolidated Cruise Ship Security - On June 1, 2015, the
public comment period for the Consolidated Cruise Ship Security Notice of
Proposed Rulemaking (NPRM) officially closed. The 115 comments have been
adjudicated and the Final Rule is being developed. The Coast Guard proposes to
amend its regulations on cruise ship terminal security and the proposed
regulations would provide detailed, flexible requirements for the screening of
all baggage, personal items, and persons—including passengers, crew, and
visitors—intended for carriage on a cruise ship. The proposed regulations would
standardize security of cruise ship terminals and eliminate redundancies in the
regulations that govern the security of cruise ship terminals.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<b><span style="font-family: Arial, Helvetica, sans-serif;">Training<o:p></o:p></span></b></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">This year, CG-FAC traveled to each District to meet with a
number of Facility Inspectors and Port Security Specialists during the FAC road
show. Program staff covered certain topics specific to the Unit, District, or
Area’s request. Hot topics were LNG as
Fuel, TWIC, MTSAII, and Cyber.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<b><span style="font-family: Arial, Helvetica, sans-serif;">Area Maritime
Security Committees<o:p></o:p></span></b></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">In April 2015, the Delaware Bay Area Maritime Security
Committee was recognized as the 2014 Area Maritime Security Committee of the
Year. This AMSC has developed a Regional Business Continuity Planning Template
which was developed by taking an all hazards approach to include commercial
risks. The template document serves as a readily implementable tool for use by
Port Stakeholders in developing their own Business Continuity Plans. Widespread
use of this template will lead to facilities better suited to maintain critical business functions
throughout our port and the nation, leading to a more secure, resilient port and the ability to
continue to contribute to the regional economy through unforeseen
circumstances.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<b><span style="font-family: Arial, Helvetica, sans-serif;">Trending Issues in
Port Safety, Security, and Resilience<o:p></o:p></span></b></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">MTSRU - In order to build system continuity and maintain
effective levels of program readiness, CG-FAC Senior Leadership developed and
incorporated a strategy with the office business plan to host a National MTSRU
Workshop every two years, to review and update program policies, guidance and
analyze lessons learned from real events to improve response effectiveness and
enhance program visibility.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">Cooperation with Transport Canada - increased cooperation in
2016.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<b><span style="font-family: Arial, Helvetica, sans-serif;">What to Expect in
2016<o:p></o:p></span></b></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">Facility Security - A policy letter encouraging facilities
to submit their FSP/VSP/ASP renewals to the Coast Guard 60 days prior to the
expiration date will be signed and disseminated to the field in CY16. Also, the
Breach of Security Instruction has been updated to include suspicious activity
response. The instruction will be published mid- 2016 and will address network
security in addition to physical security incidents. Finally, be on the lookout
for NVIC 03-03, Change 3 as well as an Alternative Security Plan NVIC in CY16.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">EHC Strategy - CG-FAC will be working with other offices to
create an Implementation Working Group for the EHC Strategy. This working group
will look to implement the four goals of the EHC Strategy including awareness,
prevention, response, and recovery.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">Cyber - CG-FAC is working on several policy updates
concerning cyber risk management. In cooperation with NIST, CG-FAC is drafting
a Cyber Framework Implementation Guide for bulk liquid facilities. This will
help facility operators identify the components of the NIST Cybersecurity
Framework most applicable to their operations. CG-FAC is also developing a NVIC
that will provide cyber risk management guidance to facility and vessel
operators. CG-FAC will continue to support the Areas on conducting Cyber
Awareness Training for CG Units.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">Exercise requirements: CG-FAC is working on policy to
clarify the definition for annual, and other time periods, as it is used in the
33 CFR 154 for exercise requirements.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">Pipeline testing: CG-FAC is updating current policy and
incorporating that into a pipeline testing policy NVIC that will guidance on
alternate testing methods.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">HOMEPORT— CG FAC is working with other Coast Guard
Headquarters Offices to complete a long overdue technical refresh of
Homeport. This update will improve reliability
and cyber security for the system and provide a better user interface.<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">Regulatory Projects:<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">Consolidated Cruise Ship Security - The public comment
period for this NPRM ended on June 1, 2015. The anticipated final rule
publication date is in 2016. <o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">Seafarer’s Access to Maritime Facilities - The public
comment period for this NPRM ended July 27, 2015. The anticipated final rule
publication date is in 2016. <o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal">
<span style="font-family: Arial, Helvetica, sans-serif;">Transportation Worker Identification Credential (TWIC)
Reader Requirements - The Final Rule is in final agency clearance.<o:p></o:p></span></div>
<div class="MsoNormal">
<br /></div>
<br />
<div class="MsoNormal">
<br /></div>
Laurie Thomashttp://www.blogger.com/profile/16611719448125721800noreply@blogger.com0tag:blogger.com,1999:blog-1555376450970352963.post-17474274550860849782016-01-29T09:06:00.000-08:002016-01-29T09:06:17.854-08:00Maritime Commons Reports on Texas AMSC Cyber Training: USCG Remarks<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">In the January
28, 2016 <a href="http://mariners.coastguard.dodlive.mil/2016/01/28/1282016-maritime-awareness-security-terrorism-training-seminar-coast-guard-remarks/">Coast
Guard Maritime Commons</a>, the Coast Guard reported on the South Texas Area
Maritime Security Committee Maritime Awareness Security Terrorism Training
Seminar focusing on Cybersecurity. Maritime Commons gave a digest of Sector Corpus
Christi’s Commander and Chair of the Area Maritime Security Committee, Capt.
Tony Hahn’s remarks. He referred to the importance of the Coast Guard’s <a href="https://www.uscg.mil/seniorleadership/DOCS/cyber.pdf">Cyber Strategy</a> and
encouraged attendees to do the following:<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoListParagraphCxSpFirst" style="margin-bottom: .0001pt; margin-bottom: 0in; mso-add-space: auto; mso-list: l0 level1 lfo1; text-indent: -.25in;">
</div>
<ul>
<li><span style="font-family: Arial, Helvetica, sans-serif; font-size: 7pt; font-stretch: normal; text-indent: -0.25in;"> </span><span style="font-family: Arial, Helvetica, sans-serif; text-indent: -0.25in;">Incorporate cybersecurity into Area Maritime
Security Committee risk assessments;</span></li>
<li><span style="font-family: Arial, Helvetica, sans-serif; font-size: 7pt; font-stretch: normal; text-indent: -0.25in;"> </span><span style="font-family: Arial, Helvetica, sans-serif; text-indent: -0.25in;">Leverage grant funding to evaluate cyber risks;</span></li>
<li><span style="font-family: Arial, Helvetica, sans-serif; font-size: 7pt; font-stretch: normal; text-indent: -0.25in;"> </span><span style="font-family: Arial, Helvetica, sans-serif; text-indent: -0.25in;">Create discreet venues to share cybersecurity
information with maritime industry;</span></li>
<li><span style="font-family: Arial, Helvetica, sans-serif; font-size: 7pt; font-stretch: normal; text-indent: -0.25in;"> </span><span style="font-family: Arial, Helvetica, sans-serif; text-indent: -0.25in;">Develop guidance for commercial vessels and
facilities on how to identify and evaluate cyber-related vulnerabilities;</span></li>
<li><span style="font-family: Arial, Helvetica, sans-serif; font-size: 7pt; font-stretch: normal; text-indent: -0.25in;"> </span><span style="font-family: Arial, Helvetica, sans-serif; text-indent: -0.25in;">Work with the International Maritime
Organization to develop global maritime cyber prevention and response
protocols;</span></li>
<li><span style="font-family: Arial, Helvetica, sans-serif; font-size: 7pt; font-stretch: normal; text-indent: -0.25in;"> </span><span style="font-family: Arial, Helvetica, sans-serif; text-indent: -0.25in;">Incorporate cybersecurity into required training
for vessel and security officers;</span></li>
<li><span style="font-family: Arial, Helvetica, sans-serif; font-size: 7pt; font-stretch: normal; text-indent: -0.25in;"> </span><span style="font-family: Arial, Helvetica, sans-serif; text-indent: -0.25in;">Incorporate cybersecurity into requirements for
Coast Guard issued mariner credentials</span></li>
</ul>
<!--[if !supportLists]--><br />
<br />
<div class="MsoListParagraphCxSpLast" style="margin-bottom: .0001pt; margin-bottom: 0in; mso-add-space: auto; mso-list: l0 level1 lfo1; text-indent: -.25in;">
<o:p></o:p></div>
Laurie Thomashttp://www.blogger.com/profile/16611719448125721800noreply@blogger.com0tag:blogger.com,1999:blog-1555376450970352963.post-71486746362003107552015-12-17T12:46:00.000-08:002015-12-17T12:46:56.604-08:00MTSA Secure and Restricted Areas<div align="center" class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in; text-align: center;">
<b><span style="font-family: Arial, Helvetica, sans-serif;">More Thoughts on the Secure
Area Concept<o:p></o:p></span></b></div>
<div align="center" class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in; text-align: center;">
<b><span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></b></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><<q: and="" area="" avoiding="" be="" confusion="" definition="" ecure="" estricted="" field.="" helpful="" in="" of="" simplified="" the="" very="" will="">> From October 2015<i> Waves on the Waterfront.<o:p></o:p></i></q:></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><i><br /></i></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;"> This was a good short general discussion of
the definitions of restricted and secure areas. However, one of the sources of
confusion about secure areas is repeated in this discussion. It appears because
it exists in the regulation, i.e., secure area as that area over which the
owner has implemented security measures for access control.<a href="file:///C:/Users/lthom_000/Desktop/secure%20areas.docx#_edn1" name="_ednref1" title=""><span class="MsoEndnoteReference"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-size: 11pt; line-height: 107%;">[1]</span></span><!--[endif]--></span></a>
Because many facilities have areas over which the owner has implemented
security measures for access control where a TWIC is not required, this
definition is puzzling. For example, the facility has a main office immediately
inside the single fence that encircles the entire facility. TWIC cards are not
required to access the office, according to the approved FSP, yet the office is
within that area over which the owner has implemented security measures for
access control. This seems to be in contradiction to the definition of secure
area. <o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">Even at this
late date, years after TWIC implementation, there is still widespread misunderstanding
about these two terms, secure and restricted areas. The idea of “secure area”
has several concepts embedded within it. <o:p></o:p></span></div>
<div class="MsoListParagraphCxSpFirst" style="margin-bottom: .0001pt; margin-bottom: 0in; mso-add-space: auto; mso-list: l0 level1 lfo1; text-indent: -.25in;">
</div>
<ul>
<li><span style="font-family: Arial, Helvetica, sans-serif; text-indent: -0.25in;">·</span><span style="font-family: Arial, Helvetica, sans-serif; font-size: 7pt; font-stretch: normal; text-indent: -0.25in;">
</span><span style="font-family: Arial, Helvetica, sans-serif; text-indent: -0.25in;">Designating areas as restricted, secure, or both
adds additional layers of security.</span><span style="font-family: Arial, Helvetica, sans-serif; text-indent: -0.25in;"> </span></li>
<li><span style="font-family: Arial, Helvetica, sans-serif; text-indent: -0.25in;">·</span><span style="font-family: Arial, Helvetica, sans-serif; font-size: 7pt; font-stretch: normal; text-indent: -0.25in;">
</span><span style="font-family: Arial, Helvetica, sans-serif; text-indent: -0.25in;">The secure area must have a maritime nexus,
because the secure area is the area where persons need a TWIC for unescorted
access and the purpose of the card itself is to ensure that only persons who
have undergone the TWIC background checks have unescorted access to these
high-risk, TSI-prone areas in facilities and vessels.</span></li>
<li><span style="font-family: Arial, Helvetica, sans-serif; text-indent: -0.25in;">·</span><span style="font-family: Arial, Helvetica, sans-serif; font-size: 7pt; font-stretch: normal; text-indent: -0.25in;">
</span><span style="font-family: Arial, Helvetica, sans-serif; text-indent: -0.25in;">Secure areas are a security measure described
out in the FSP so to a certain extent they can be fluid across the system, and
are subject to the judgement of the individual Coast Guard unit that approves
the FSP.</span><span style="font-family: Arial, Helvetica, sans-serif; text-indent: -0.25in;"> </span><span style="font-family: Arial, Helvetica, sans-serif; text-indent: -0.25in;">The only secure area that will
be guaranteed to be designated as such across the system, from the largest
facility in the country to Laurie’s Sand & Gravel Dock, is the area
immediately adjacent the vessel (that triggers the FSP) when the vessel is at
the dock.</span><a href="file:///C:/Users/lthom_000/Desktop/secure%20areas.docx#_edn2" name="_ednref2" style="font-family: Arial, Helvetica, sans-serif; text-indent: -0.25in;" title=""><span class="MsoEndnoteReference"><span class="MsoEndnoteReference"><span style="font-size: 11pt; line-height: 107%;">[2]</span></span></span></a></li>
</ul>
<!--[if !supportLists]--><br />
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">For purposes
of clarification, it might be useful if 33 CFR 101.105 be amended to read
“Secure area means the area on board a vessel or at a facility or outer
continental shelf facility over which the owner/operator has implemented
security measures for access control <i>where
a TWIC card is required for unescorted access</i>, in accordance with a Coast
Guard approved security plan.” In all secure areas, TWIC cards are required for
unescorted access. It seems odd therefore to exclude this important concept
from the definition. <o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">To keep the two
concepts clear in the mind, it is less helpful to contrast them than to simply
remember the following:<o:p></o:p></span></div>
<div class="MsoListParagraphCxSpFirst" style="margin-bottom: .0001pt; margin-bottom: 0in; mso-add-space: auto; mso-list: l1 level1 lfo2; text-indent: -.25in;">
</div>
<ul>
<li><span style="font-family: Arial, Helvetica, sans-serif; text-indent: -0.25in;">·</span><span style="font-family: Arial, Helvetica, sans-serif; font-size: 7pt; font-stretch: normal; text-indent: -0.25in;">
</span><span style="font-family: Arial, Helvetica, sans-serif; text-indent: -0.25in;">Restricted areas require limited access and a
higher degree of security protection</span><a href="file:///C:/Users/lthom_000/Desktop/secure%20areas.docx#_edn3" name="_ednref3" style="font-family: Arial, Helvetica, sans-serif; text-indent: -0.25in;" title=""><span class="MsoEndnoteReference"><span class="MsoEndnoteReference"><span style="font-size: 11pt; line-height: 107%;">[3]</span></span></span></a><span style="font-family: Arial, Helvetica, sans-serif; text-indent: -0.25in;">;
a</span><span style="font-family: Arial, Helvetica, sans-serif; text-indent: -0.25in;"> </span><span style="font-family: Arial, Helvetica, sans-serif; text-indent: -0.25in;">list of areas that must be designated
as restricted, as appropriate for the facility, is</span><span style="font-family: Arial, Helvetica, sans-serif; text-indent: -0.25in;"> </span><span style="font-family: Arial, Helvetica, sans-serif; text-indent: -0.25in;">given in 33 CFR 105.260(b).</span></li>
<li><span style="font-family: Arial, Helvetica, sans-serif; text-indent: -0.25in;">·</span><span style="font-family: Arial, Helvetica, sans-serif; font-size: 7pt; font-stretch: normal; text-indent: -0.25in;">
</span><span style="font-family: Arial, Helvetica, sans-serif; text-indent: -0.25in;">Secure areas are those areas where persons need
a TWIC for unescorted access. There can be no secure area that is not connected
with TWIC card use.</span></li>
</ul>
<!--[if !supportLists]--><br />
<br />
<div>
<!--[if !supportEndnotes]--><span style="font-family: Arial, Helvetica, sans-serif;"><br clear="all" />
</span><hr align="left" size="1" width="33%" />
<!--[endif]-->
<div id="edn1">
<div class="MsoEndnoteText">
<span style="font-family: Arial, Helvetica, sans-serif;"><a href="file:///C:/Users/lthom_000/Desktop/secure%20areas.docx#_ednref1" name="_edn1" title=""><span class="MsoEndnoteReference"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-size: 10pt; line-height: 107%;">[1]</span></span><!--[endif]--></span></a> 33
CFR 101.105, definition of secure area.<o:p></o:p></span></div>
</div>
<div id="edn2">
<div class="MsoEndnoteText">
<span style="font-family: Arial, Helvetica, sans-serif;"><a href="file:///C:/Users/lthom_000/Desktop/secure%20areas.docx#_ednref2" name="_edn2" title=""><span class="MsoEndnoteReference"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-size: 10pt; line-height: 107%;">[2]</span></span><!--[endif]--></span></a> Navigation and Inspection Circular 03-07, enc.
3.<o:p></o:p></span></div>
</div>
<div id="edn3">
<div class="MsoEndnoteText">
<span style="font-family: Arial, Helvetica, sans-serif;"><a href="file:///C:/Users/lthom_000/Desktop/secure%20areas.docx#_ednref3" name="_edn3" title=""><span class="MsoEndnoteReference"><!--[if !supportFootnotes]--><span class="MsoEndnoteReference"><span style="font-size: 10pt; line-height: 107%;">[3]</span></span><!--[endif]--></span></a> 33
CFR 101.105, definition of restricted area.</span><o:p></o:p></div>
</div>
</div>
Laurie Thomashttp://www.blogger.com/profile/16611719448125721800noreply@blogger.com0tag:blogger.com,1999:blog-1555376450970352963.post-65010371233574321002015-12-16T08:28:00.000-08:002015-12-16T08:28:46.475-08:00<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">On December
15 2015, the Department of Homeland Security issued its Semiannual Regulatory
Agenda. As Dennis Bryant so aptly puts it, “this agenda is aspirational in
nature.” This means DHS <b><i>hopes</i></b> that the given timetables will be met. Below is
MTSA-related information from the Agenda, with my comments. The full agenda can
be found at https://www.gpo.gov/fdsys/pkg/FR-2015-12-15/pdf/2015-30621.pdf</span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<b><br /></b></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b>Updates to
Maritime Security</b><o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">Abstract:
The Coast Guard proposes certain additions, changes, and amendments to 33 CFR,
subchapter H. Subchapter H is comprised of parts 101 through 106. Subchapter H
implements the major provisions of the Maritime Transportation Security Act of
2002 (MTSA). This rulemaking is the first major revision to subchapter H. The
proposed changes would further the goals of domestic compliance and international
cooperation by incorporating requirements from legislation implemented since
the<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">original
publication of these regulations, such as the Security and Accountability for
Every (SAFE) Port Act of 2006, and including international standards such as
Standards of Training, Certification & </span><span style="font-family: Arial, Helvetica, sans-serif;">Watchkeeping
security training. This rulemaking has international interest because of the
close relationship between subchapter H and the International Ship and Port
Security Code (ISPS).</span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">NPRM
.................. 07/00/16<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">Comments: At
this point, I can’t speculate when this update will be issued, or how outdated
it will be when it finally comes out. It’s
obvious to MTSA practitioners that an update needs to be made. Absent this
update, industry and regulators end up operating from NVICs and PACs and policy
letters and other documents, not an ideal situation from either
an industry or a regulator’s point of view. PACs and letters under CF-FAC
signature aren’t regulations. They lack the industry comment that is an
integral part of the regulatory process. The regulatory process seems to have
evolved into a process too cumbersome for today’s fast moving workplace.<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b>Seafarers’
Access to Maritime Facilities</b><o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">Abstract:
This regulatory action will implement section 811 of the Coast Guard
Authorization Act of 2010 (Pub. L. 111–281), which requires the owner/operator
of a facility regulated by the Coast Guard under the Maritime Transportation
Security Act of 2002 (Pub. L. 107–295) (MTSA) to provide a system that enables
seafarers and certain other individuals to transit between vessels moored at
the facility and the<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">facility
gate in a timely manner at no cost to the seafarer or other individual. Ensuring
that such access through a facility is consistent with the security requirements
in MTSA is part of the Coast Guard’s Ports, Waterways, and Coastal Security
(PWCS) mission.<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;"> The timetable on this rule is:<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;"> NPRM .................. 12/29/14 <o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">NPRM Comment
Period Reopened…05/27/15 <o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">NPRM Comment
Period End…07/01/15<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">Final Rule
............ 02/00/16<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">Comments: I would not be surprised to see this final
rule issued in first quarter 2016. This regulation will (almost certainly) require
action on the part of all MTSA facilities, including a new FSP section. Interesting
example of a narrowly-focused regulation that sped through the process, despite
an extended comment period. We need to keep in mind, however, the many Coast
Guard actions that preceded this reg.<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><b>Transportation
Worker Identification Credential (TWIC); Card Reader Requirement</b><o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">Concerning the
TWIC Reader rule (Transportation Worker Identification Credential (TWIC); Card
Reader Requirement) the Agenda states: Regulatory Plan: This entry is Seq. No.
62 in part II of this issue of the Federal Register.<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<br />
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">Comment:
There is no Part II to this issue of the FR, so I am assuming that this is just
one more puzzling aspect of the TWIC
program.</span><o:p></o:p></div>
Laurie Thomashttp://www.blogger.com/profile/16611719448125721800noreply@blogger.com0tag:blogger.com,1999:blog-1555376450970352963.post-69560079977377621092015-11-30T13:30:00.000-08:002015-11-30T13:30:01.656-08:00Big Changes Coming Soon to Coast Guard's Homeport Website<div class="MsoNormal" style="background: white; margin-bottom: 12pt;">
<span style="color: #333333; font-family: "Arial",sans-serif; mso-fareast-font-family: "Times New Roman";">On November 27, 2015, the Coast Guard made an announcement
concerning its Homeport website via Maritime Commons (<a href="http://mariners.coastguard.dodlive.mil/2015/11/27/11272015-homeport-2-0-news-and-information/">http://mariners.coastguard.dodlive.mil/2015/11/27/11272015-homeport-2-0-news-and-information/</a>
). The information is also posted on the Homeport website, <a href="http://homeport.uscg.mil/">http://homeport.uscg.mil</a> .<o:p></o:p></span></div>
<div class="MsoNormal" style="background: white; margin-bottom: 12pt;">
<span style="color: #333333; font-family: "Arial",sans-serif; mso-fareast-font-family: "Times New Roman";">We have been hearing for quite a while about
upcoming changes to Homeport – these changes are happening and happening soon.
Below is the text of the announcement from the Homeport/CG-FAC website:<o:p></o:p></span></div>
<div class="MsoNormal" style="background: white; margin-bottom: 12pt;">
<span style="color: #333333; font-family: "Arial",sans-serif; mso-fareast-font-family: "Times New Roman";">“</span><span lang="X-NONE" style="color: #333333; font-family: "Arial",sans-serif; mso-ansi-language: X-NONE; mso-fareast-font-family: "Times New Roman";">The </span><span style="color: #333333; font-family: "Arial",sans-serif; mso-fareast-font-family: "Times New Roman";">United States Coast
Guard (USCG) Homeport Internet Portal (HIP) was established in 2005 to
facilitate compliance with the requirements set forth in the Maritime
Transportation Security Act (MTSA) of 2002, by providing secure information
dissemination, advanced collaboration, electronic submission and approval for
vessel and facility security plans, and complex electronic and
telecommunication notification capabilities.<o:p></o:p></span></div>
<div class="MsoNormal" style="background: white; margin-bottom: 12pt;">
<span lang="X-NONE" style="color: #333333; font-family: "Arial",sans-serif; mso-ansi-language: X-NONE; mso-fareast-font-family: "Times New Roman";">Since its inception, </span><span style="color: #333333; font-family: "Arial",sans-serif; mso-fareast-font-family: "Times New Roman";">HIP</span><span lang="X-NONE" style="color: #333333; font-family: "Arial",sans-serif; mso-ansi-language: X-NONE; mso-fareast-font-family: "Times New Roman";"> has
been expanded to provide additional support such as Transportation Worker
Identification Card New Hire; Electronic Vessel Response Plan; Marine Event
Permit Process; Port Status Indicator; Merchant Mariner Licensing and
Documentation; Marine Training and Assessment Data (training documentation);
Merchant Mariner Certificate; Sea Service Calculator; Merchant Mariner
Verification of Certificates; and Merchant Mariner Credential Survey</span><span style="color: #333333; font-family: "Arial",sans-serif; mso-fareast-font-family: "Times New Roman";"><o:p></o:p></span></div>
<div class="MsoNormal" style="background: white; margin-bottom: 12pt;">
<span style="color: #333333; font-family: "Arial",sans-serif; mso-fareast-font-family: "Times New Roman";">The Coast Guard will launch Homeport 2.0 Jan. 29, 2016
in order to provide a better user experience and improve the security of user
information. Upgrades will include fewer site navigation menus and more
efficient and secure search functions.<o:p></o:p></span></div>
<div class="MsoNormal" style="background: white; margin-bottom: 12pt;">
<span style="color: #333333; font-family: "Arial",sans-serif; mso-fareast-font-family: "Times New Roman";">Although most features will be available as
soon as the new site launches, user access to a few conveniences may be
interrupted. Review the <a href="http://www.uscg.mil/hq/cg5/cg544/docs/Homeport%20Application%20Deployment%20Schedule.pdf"><span style="color: #003366;">Homeport 2.0 Deployment Schedule</span></a> for
details. Functions that are essential to maintaining port security or that are
critical to continuing the flow of commerce will remain available during the
transition period.<o:p></o:p></span></div>
<div class="MsoNormal" style="background: white; margin-bottom: 12pt;">
<span style="color: #333333; font-family: "Arial",sans-serif; mso-fareast-font-family: "Times New Roman";">Alternative solutions are available for most
features taken offline during the transition. Anyone who needs access to a
service normally obtained through HIP should contact the appropriate subject
matter expert listed in the <a href="http://www.uscg.mil/hq/cg5/cg544/docs/Homeport%20Application%20Deployment%20Schedule.pdf"><span style="color: #003366;">Homeport 2.0 Deployment Schedule</span></a>.<o:p></o:p></span></div>
<div class="MsoNormal">
<u><span style="font-family: "Arial",sans-serif;">From the
Deployment Schedule:<o:p></o:p></span></u></div>
<div class="MsoNormal">
<b><i><span style="font-family: "Arial",sans-serif;">Uninterrupted services:<o:p></o:p></span></i></b></div>
<div class="MsoNormal">
<span style="font-family: "Arial",sans-serif;"> </span><span style="font-family: Symbol; mso-ascii-font-family: Arial; mso-bidi-font-family: Arial; mso-char-type: symbol; mso-hansi-font-family: Arial; mso-symbol-font-family: Symbol;">·</span><span style="font-family: "Arial",sans-serif;"> TWIC new hire procedures <o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Symbol; mso-ascii-font-family: Arial; mso-bidi-font-family: Arial; mso-char-type: symbol; mso-hansi-font-family: Arial; mso-symbol-font-family: Symbol;">·</span><span style="font-family: "Arial",sans-serif;"> Port
status query<o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: "Arial",sans-serif;"> </span><span style="font-family: Symbol; mso-ascii-font-family: Arial; mso-bidi-font-family: Arial; mso-char-type: symbol; mso-hansi-font-family: Arial; mso-symbol-font-family: Symbol;">·</span><span style="font-family: "Arial",sans-serif;"> Merchant Mariner Application Status <o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Symbol; mso-ascii-font-family: Arial; mso-bidi-font-family: Arial; mso-char-type: symbol; mso-hansi-font-family: Arial; mso-symbol-font-family: Symbol;">·</span><span style="font-family: "Arial",sans-serif;"> VRP
Express <o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Symbol; mso-ascii-font-family: Arial; mso-bidi-font-family: Arial; mso-char-type: symbol; mso-hansi-font-family: Arial; mso-symbol-font-family: Symbol;">·</span><span style="font-family: "Arial",sans-serif;"> Vessels
& facilities search <o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Symbol; mso-ascii-font-family: Arial; mso-bidi-font-family: Arial; mso-char-type: symbol; mso-hansi-font-family: Arial; mso-symbol-font-family: Symbol;">·</span><span style="font-family: "Arial",sans-serif;"> Merchant
Mariner Credential Verification <o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Symbol; mso-ascii-font-family: Arial; mso-bidi-font-family: Arial; mso-char-type: symbol; mso-hansi-font-family: Arial; mso-symbol-font-family: Symbol;">·</span><span style="font-family: "Arial",sans-serif;"> Merchant
Mariner Sea Service Calculator <o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Symbol; mso-ascii-font-family: Arial; mso-bidi-font-family: Arial; mso-char-type: symbol; mso-hansi-font-family: Arial; mso-symbol-font-family: Symbol;">·</span><span style="font-family: "Arial",sans-serif;"> Most core
CG accessible-only functions <o:p></o:p></span></div>
<div class="MsoNormal">
<b><i><span style="font-family: "Arial",sans-serif;">Services unavailable Jan.
29 - March 31, 2016 <o:p></o:p></span></i></b></div>
<div class="MsoNormal">
<span style="font-family: Symbol; mso-ascii-font-family: Arial; mso-bidi-font-family: Arial; mso-char-type: symbol; mso-hansi-font-family: Arial; mso-symbol-font-family: Symbol;">·</span><span style="font-family: "Arial",sans-serif;"> Mariner
Training & Assessment Database <o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: "Arial",sans-serif;"> </span><span style="font-family: Symbol; mso-ascii-font-family: Arial; mso-bidi-font-family: Arial; mso-char-type: symbol; mso-hansi-font-family: Arial; mso-symbol-font-family: Symbol;">·</span><span style="font-family: "Arial",sans-serif;"> Security Plans Temporary <o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Symbol; mso-ascii-font-family: Arial; mso-bidi-font-family: Arial; mso-char-type: symbol; mso-hansi-font-family: Arial; mso-symbol-font-family: Symbol;">·</span><span style="font-family: "Arial",sans-serif;"> Merchant
Mariner Credential Survey <o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: "Arial",sans-serif;"> <b><i>Services unavailable Jan. 29 - April 30,
2016<o:p></o:p></i></b></span></div>
<div class="MsoNormal">
<span style="font-family: "Arial",sans-serif;"> </span><span style="font-family: Symbol; mso-ascii-font-family: Arial; mso-bidi-font-family: Arial; mso-char-type: symbol; mso-hansi-font-family: Arial; mso-symbol-font-family: Symbol;">·</span><span style="font-family: "Arial",sans-serif;"> Merchant Mariner Certificate <o:p></o:p></span></div>
<div class="MsoNormal">
<span style="font-family: Symbol; mso-ascii-font-family: Arial; mso-bidi-font-family: Arial; mso-char-type: symbol; mso-hansi-font-family: Arial; mso-symbol-font-family: Symbol;">·</span><span style="font-family: "Arial",sans-serif;"> Marine
Event Application Temporary <o:p></o:p></span></div>
<br />
<div class="MsoNormal">
<span style="font-family: "Arial",sans-serif;">The FAQ
document (<a href="http://www.uscg.mil/hq/cg5/cg544/docs/Homeport_2%200_FAQs_AllUsers1%201.pdf">http://www.uscg.mil/hq/cg5/cg544/docs/Homeport_2%200_FAQs_AllUsers1%201.pdf</a>)
lists work-arounds for most unavailable services in a Deployment Schedule (<a href="http://www.uscg.mil/hq/cg5/cg544/docs/Homeport%20Application%20Deployment%20Schedule.pdf">http://www.uscg.mil/hq/cg5/cg544/docs/Homeport%20Application%20Deployment%20Schedule.pdf</a>
). There is a separate FAQ document (<a href="http://www.uscg.mil/hq/cg5/cg544/docs/Homeport_2%200_FAQs_CommunityOwners1%201.pdf">http://www.uscg.mil/hq/cg5/cg544/docs/Homeport_2%200_FAQs_CommunityOwners1%201.pdf</a>
) for community owners, who need to pay careful attention to deadlines. The
deadline for migrating community content is January 29, 2016. This is a hard deadline. “Legacy Homeport
will be taken offline as of Jan. 29, 2016, and community owners should make all
efforts to meet this deadline. Any content that is not transferred will be
auto-archived and will not be easily accessible.”<o:p></o:p></span></div>
Laurie Thomashttp://www.blogger.com/profile/16611719448125721800noreply@blogger.com0tag:blogger.com,1999:blog-1555376450970352963.post-44744805909226284032015-06-18T16:04:00.001-07:002015-06-18T16:04:27.296-07:00Coast Guard Releases Cyber Strategy <div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">On June 16,
2015, the U.S. Coast Guard issued its Cyber Strategy. The document may be found at http://www.uscg.mil/seniorleadership/DOCS/cyber.pdf.
<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">The document
opens with a sobering statement of the problem: “Cybersecurity* is one of the
most serious economic and national security challenges we face as a Nation.
Government systems—including Coast Guard systems—face a mounting array of
emerging cyber threats that could severely compromise and limit our Service’s ability
to perform our essential missions.” “In the digital age…there is no strategic
objective the Coast Guard can adequately meet—or operational mission the Coast
Guard can fully perform—without a robust and comprehensive cyber program.*”<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">The asterisks
link to definitions, and this document gives us a good range of definitions of
cyber-related terms. Definitions, so
important to the MTSA community, are found in Appendix I, and definitions
sources are from a variety of documents and explain many cyber-related terms,
including: <o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">Cybersecurity breach – Unauthorized
access to data, applications, services, networks and/or devices, by-passing their
underlying security mechanisms. A cybersecurity breach that may rise to the
level of a reportable Maritime Transportation Security Act (MTSA) security
breach occurs when an individual, an entity, or an application illegitimately
enters a private or confidential Information Technology perimeter of a
MTSA-regulated facility or vessel, Maritime Critical Infrastructure/Key
Resources, or industrial control system such as Supervisory Control and Data
Acquisition systems, including but not limited to terminal operating systems,
global positioning systems, and cargo management systems. <o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in; margin-left: .5in; margin-right: 0in; margin-top: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">Reproduced
in its entirety below is the Executive Summary. Port security stakeholders are
encouraged to read the entire document.<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">The Coast
Guard is committed to ensuring the safety, security, and stewardship of our
Nation’s </span><span style="font-family: Arial, Helvetica, sans-serif;">waters. This
commitment requires a comprehensive cyber strategy that provides a clear
framework </span><span style="font-family: Arial, Helvetica, sans-serif;">for our
overall mission success.</span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">Cyber
technology has fueled great progress and efficiency in our modern world. Coast
Guard </span><span style="font-family: Arial, Helvetica, sans-serif;">operations
are more effective because of the rapid evolution in cyber technology, and
advanced </span><span style="font-family: Arial, Helvetica, sans-serif;">technologies
have also led to an unprecedented era of efficiency of the Maritime
Transportation </span><span style="font-family: Arial, Helvetica, sans-serif;">System
(MTS). However, with these benefits come serious risks. Information and its
supporting </span><span style="font-family: Arial, Helvetica, sans-serif;">systems are
continually attacked and exploited by hostile actors. Foreign governments,
criminal </span><span style="font-family: Arial, Helvetica, sans-serif;">organizations,
and other illicit actors attempt to infiltrate critical government and private
sector </span><span style="font-family: Arial, Helvetica, sans-serif;">information
systems, representing one of the most serious threats we face as a nation.</span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">As the Coast
Guard relies on modern digital information and communications systems to
execute </span><span style="font-family: Arial, Helvetica, sans-serif;">its
missions, the Service must defend against those who threaten them. The Coast
Guard must </span><span style="font-family: Arial, Helvetica, sans-serif;">also build
and sustain an operational advantage in cyberspace to ensure optimal
integration of </span><span style="font-family: Arial, Helvetica, sans-serif;">information
and intelligence with our operations. Moreover, the Coast Guard must lead the
effort </span><span style="font-family: Arial, Helvetica, sans-serif;">to protect
maritime critical infrastructure from a broadening array of cyber threats.</span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;"><br /></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">To fully
ensure the Coast Guard is able to perform its essential missions in the 21st
Century, it </span><span style="font-family: Arial, Helvetica, sans-serif;">must fully
embrace cyberspace as an operational domain. To this end, the Coast Guard will focus </span><span style="font-family: Arial, Helvetica, sans-serif;">on three
specific strategic priorities in the cyber domain over the next ten years:</span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">• Defending Cyberspace<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">• Enabling Operations<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">• Protecting Infrastructure<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">Defending
Cyberspace: Secure and resilient Coast Guard IT systems and networks are
essential </span><span style="font-family: Arial, Helvetica, sans-serif;">for overall
mission success. To ensure the full scope of Coast Guard capabilities are as
effective </span><span style="font-family: Arial, Helvetica, sans-serif;">and
efficient as possible, the Coast Guard must serve as a model agency in
protecting information </span><span style="font-family: Arial, Helvetica, sans-serif;">infrastructure
and building a more resilient Coast Guard network.</span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">Enabling
Operations: To operate effectively within the cyber domain, the Coast Guard
must<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">develop and
leverage a diverse set of cyber capabilities and authorities. Cyberspace
operations, </span><span style="font-family: Arial, Helvetica, sans-serif;">inside and
outside Coast Guard information and communications networks and systems, can
help </span><span style="font-family: Arial, Helvetica, sans-serif;">detect,
deter, disable, and defeat adversaries. Robust intelligence, law enforcement,
and maritime </span><span style="font-family: Arial, Helvetica, sans-serif;">and military
cyber programs are essential to enhancing the effectiveness of Coast Guard
operations, </span><span style="font-family: Arial, Helvetica, sans-serif;">and
deterring, preventing, and responding to malicious activity targeting critical
maritime </span><span style="font-family: Arial, Helvetica, sans-serif;">infrastructure.
Coast Guard leaders must recognize that cyber capabilities are a critical
enabler </span><span style="font-family: Arial, Helvetica, sans-serif;">of success
across all missions, and ensure that these capabilities are leveraged by
commanders and </span><span style="font-family: Arial, Helvetica, sans-serif;">decision-makers
at all levels.</span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">Protecting
Infrastructure: Maritime critical infrastructure and the MTS are vital to our<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">economy,
national security, and national defense. The MTS includes ocean carriers,
coastwise </span><span style="font-family: Arial, Helvetica, sans-serif;">shipping
along our shores, the Western Rivers and Great Lakes, and the Nation’s ports
and </span><span style="font-family: Arial, Helvetica, sans-serif;">terminals.
Cyber systems enable the MTS to operate with unprecedented speed and
efficiency. </span><span style="font-family: Arial, Helvetica, sans-serif;">Those same
cyber systems also create potential vulnerabilities. As the maritime
transportation </span><span style="font-family: Arial, Helvetica, sans-serif;">Sector
Specific Agency (as defined by the National Infrastructure Protection Plan),
the Coast </span><span style="font-family: Arial, Helvetica, sans-serif;">Guard must
lead the unity of effort required to protect maritime critical infrastructure
from </span><span style="font-family: Arial, Helvetica, sans-serif;">attacks,
accidents, and disasters.</span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<br /></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">Ensuring
Long-term Success: In support of the three strategic priorities, this Strategy<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">identifies a
number of cross-cutting support factors that will ensure the Coast Guard’s
long-term </span><span style="font-family: Arial, Helvetica, sans-serif;">success in
meeting the Service's strategic goals in the cyber domain. These include:</span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">(1)
recognition of cyberspace as an operational domain,<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">(2)
developing cyber guidance and defining mission space,<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">(3)
leveraging partnerships to build knowledge, resource capacity,<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">and an
understanding of MTS cyber vulnerabilities,<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">(4) sharing
of real-time information,<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">(5)
organizing for success,<o:p></o:p></span></div>
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">(6) building
a well-trained cyber workforce, and<o:p></o:p></span></div>
<br />
<div class="MsoNormal" style="margin-bottom: .0001pt; margin-bottom: 0in;">
<span style="font-family: Arial, Helvetica, sans-serif;">(7) making
thoughtful future cyber investments.</span><o:p></o:p></div>
Laurie Thomashttp://www.blogger.com/profile/16611719448125721800noreply@blogger.com0