<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:dc="https://purl.org/dc/elements/1.1/"
     xmlns:dcterms="http://purl.org/dc/terms/"
     xmlns:media="http://search.yahoo.com/mrss/"
     xmlns:atom="http://www.w3.org/2005/Atom"
>
    <channel>
                    <atom:link href="https://www.tvtechnology.com/feeds/tag/tls-1-2" rel="self" type="application/rss+xml" />
                            <title><![CDATA[ Latest from Tv Technology in Tls-1-2 ]]></title>
                <link>https://www.tvtechnology.com/tag/tls-1-2</link>
        <description><![CDATA[ All the latest tls-1-2 content from the Tv Technology team ]]></description>
                                    <lastBuildDate>Thu, 10 Oct 2019 17:58:08 +0000</lastBuildDate>
                            <language>en</language>
                                <item>
                                                            <title><![CDATA[ Broadcasters Need to Keep Eye on Latest EAS Updates ]]></title>
                                                                                                                                                                                                <link>https://www.tvtechnology.com/news/broadcasters-need-to-keep-eye-on-latest-eas-updates</link>
                                                                            <description>
                            <![CDATA[ The new TLS protocol update needed before Nov. 8. ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">9EEoJtBKA2ng2F7ogJaaCL</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/2frp25jWm24SGH8zmRjdAd-1280-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Thu, 10 Oct 2019 17:58:08 +0000</pubDate>                                                                                                                                                                                                                                <category><![CDATA[Security]]></category>
                                                    <category><![CDATA[Infrastructure]]></category>
                                                                                                <author><![CDATA[ sashworth@sbcglobal.net (Susan Ashworth) ]]></author>                    <dc:creator><![CDATA[ Susan Ashworth ]]></dc:creator>                                                                                    <dc:source><![CDATA[ http://cdn.mos.cms.futurecdn.net/7WrKnyfZTKsexwpR7E6V4R.jpeg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                                                                                                                                <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/2frp25jWm24SGH8zmRjdAd-1280-80.jpg">
                                                            <media:credit><![CDATA[null]]></media:credit>
                                                                                                                                                                                                                                                                                                                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/2frp25jWm24SGH8zmRjdAd-1280-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p><strong>WASHINGTON</strong><strong>—</strong>It’s time for broadcasters to confirm that their stations are up and running with the latest in EAS updates.</p><figure class="van-image-figure pull-" data-bordeaux-image-check ><div class='image-full-width-wrapper'><div class='image-widthsetter' ><p class="vanilla-image-block" style="padding-top:56.25%;"><img id="2frp25jWm24SGH8zmRjdAd" name="" alt="" src="https://cdn.mos.cms.futurecdn.net/2frp25jWm24SGH8zmRjdAd.jpg" mos="https://cdn.mos.cms.futurecdn.net/2frp25jWm24SGH8zmRjdAd.jpg" align="" fullscreen="" width="" height="" attribution="" endorsement="" class="pull-"></p></div></div></figure><p>As it stands today, EAS participants are required to not only receive Common Alert Protocol messages from IPAWS but also configure their systems to reject all CAP-formatted EAS messages that include an invalid digital signature. Now, an effort to maintain compliance with commonly accepted security standards, FEMA is also taking the next step of removing support for older methods by requiring the use of an updated TLS 1.2 protocol to access FEMA’s IPAWS server, said Sage Alerting Systems and the Society of Broadcast Engineers. </p><p>TLS, or Transport Layer Security, is cryptographic protocol providing communications security over networks and is often used for internet communications.</p><p>To acquire and verify IPAWS CAP alerts, a broadcaster’s EAS alerting equipment must be upgraded with the TLS 1.2 update prior to Nov. 8, 2019.</p><p>The move is one of several rule changes put in place by the Federal Communications Commission and the Federal Emergency Management Agency to improve EAS security to ensure that messages are received smoothly and accurately.</p><p>According to Sage, the TLS 1.2 protocol is now part of a September 2019 update called Rev95. Certain ENDEC systems qualify for a free update; older systems will need to purchase an update <a href="https://www.sagealertingsystems.com/Distributors.htm">via a distributor</a>.</p><p>SBE cautioned in its <a href="https://blog.sbe.org/category/legislative-update/emergency-alert-system/">blog</a> that after the switchover on Nov. 8, older versions of the ENDEC software will not be able to receive CAP messages from IPAWS. “This will render the station in violation of FCC rules concerning EAS monitoring and logging,” SBE said.</p><p>For Gorman-Redlich systems, the SBE reported that stations operating with E-prom V 9.5.8 will remain compliant with the changes. For Digital Alert Systems DASDEC/One-Net systems, those units operating with software versions 3.1 or 4.0 will remain compliant.</p><p>In addition to the CAP format changes, the SBE said the FCC also recently changed EAS rules to refine the time window within which an alert message is valid and added a new false EAS alert reporting rule.</p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
            </channel>
</rss>