<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:dc="http://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"
     xmlns:cf="https://www.futureplc.com/rss/content-flags"
>
    <channel>
                    <atom:link href="https://www.tvtechnology.com/feeds/tag/sage-endec" rel="self" type="application/rss+xml" />
                            <title><![CDATA[ Latest from Tv Technology in Sage-endec ]]></title>
                <link>https://www.tvtechnology.com/tag/sage-endec</link>
        <description><![CDATA[ All the latest sage-endec content from the Tv Technology team ]]></description>
                                    <lastBuildDate>Thu, 09 Jul 2026 19:43:22 +0000</lastBuildDate>
                            <language>en</language>
                                <item>
                                                            <title><![CDATA[ Sage Offers Guidance on EAS Password Changes ]]></title>
                                                                                                <dc:content><![CDATA[ <p>Sage Alerting has issued a technical note regarding <a href="https://www.tvtechnology.com/tag/emergency-alert-system">Emergency Alert System</a> passwords.</p><p>In response to the <a href="https://www.radioworld.com/news-and-business/business-and-law/does-your-eas-gear-meet-these-new-requirements" target="_blank">Federal Communications Commission’s recent rule change</a>, it sent an email to users of the Sage Digital ENDEC model 3644. It applies only to users in the United States.</p><p>“Important: If you are changing your ENDEC’s password to meet the new FCC requirements, do not use the ampersand (&) or plus (+) character in your new password,” it states.</p><p>The FCC will now require that stations and other EAS participants use a strong password with at least 15 characters. It said to avoid common words or using the same password for other purposes.</p><p>Security updates must be installed promptly, and stations must use firewalls or other network segmentation. </p><p>“While these rules take effect 60 days after publication in the Federal Register, these are commonly accepted cybersecurity rules,” Sage wrote. “There is no reason to wait.” </p><p>The company said it plans a free software update this year that fixes bugs and will permit the use of & and + in the password. </p><p>“You do not need to wait for that update to implement the new password requirements if you avoid those characters.” </p><p>The <a href="https://docs.fcc.gov/public/attachments/FCC-26-38A1.pdf" target="_blank">complete report and order is here</a>. And Sage has posted specific <a href="https://www.sagealertingsystems.com/fcc2026.pdf" target="_blank">guidance for its users here</a>.</p><p><em><strong>This article was intially published by our sister publication </strong></em><a href="https://www.radioworld.com" target="_blank"><em><strong>Radio World</strong></em></a><em><strong>. </strong></em></p><p></p> ]]></dc:content>
                                                                                                                                            <link>https://www.tvtechnology.com/regulatory-legal/sage-offers-guidance-on-eas-password-changes</link>
                                                                            <description>
                            <![CDATA[ Don’t use (&) or (+) for now ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">tQgrwr5SufFqH22SEaMQPJ</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/LqvVNDPe6DLMs7rt6ecD6H-1280-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Thu, 09 Jul 2026 19:43:22 +0000</pubDate>                                                                                                                                                                                                                                <category><![CDATA[Regulatory & Legal]]></category>
                                                    <category><![CDATA[FCC]]></category>
                                                                                                                    <dc:creator><![CDATA[ Radio World Staff ]]></dc:creator>                                                                                                        <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/LqvVNDPe6DLMs7rt6ecD6H-1280-80.jpg">
                                                            <media:credit><![CDATA[Sage Alerting Systems]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Sage Alerting Systems logo]]></media:description>                                                            <media:text><![CDATA[Sage Alerting Systems logo]]></media:text>
                                <media:title type="plain"><![CDATA[Sage Alerting Systems logo]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/LqvVNDPe6DLMs7rt6ecD6H-1280-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>Sage Alerting has issued a technical note regarding <a href="https://www.tvtechnology.com/tag/emergency-alert-system">Emergency Alert System</a> passwords.</p><p>In response to the <a href="https://www.radioworld.com/news-and-business/business-and-law/does-your-eas-gear-meet-these-new-requirements" target="_blank">Federal Communications Commission’s recent rule change</a>, it sent an email to users of the Sage Digital ENDEC model 3644. It applies only to users in the United States.</p><p>“Important: If you are changing your ENDEC’s password to meet the new FCC requirements, do not use the ampersand (&) or plus (+) character in your new password,” it states.</p><p>The FCC will now require that stations and other EAS participants use a strong password with at least 15 characters. It said to avoid common words or using the same password for other purposes.</p><p>Security updates must be installed promptly, and stations must use firewalls or other network segmentation. </p><p>“While these rules take effect 60 days after publication in the Federal Register, these are commonly accepted cybersecurity rules,” Sage wrote. “There is no reason to wait.” </p><p>The company said it plans a free software update this year that fixes bugs and will permit the use of & and + in the password. </p><p>“You do not need to wait for that update to implement the new password requirements if you avoid those characters.” </p><p>The <a href="https://docs.fcc.gov/public/attachments/FCC-26-38A1.pdf" target="_blank">complete report and order is here</a>. And Sage has posted specific <a href="https://www.sagealertingsystems.com/fcc2026.pdf" target="_blank">guidance for its users here</a>.</p><p><em><strong>This article was intially published by our sister publication </strong></em><a href="https://www.radioworld.com" target="_blank"><em><strong>Radio World</strong></em></a><em><strong>. </strong></em></p><p></p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Cable Industry Backs Broadcasters’ Move to Software-Based EAS ]]></title>
                                                                                                <dc:content><![CDATA[ <p>The cable industry has <a href="https://www.fcc.gov/ecfs/document/105021871028974/1">told</a> the Federal Communications Commission it supports the National Association of Broadcasters’ proposal to allow broadcasters to use software-based Emergency Alert Systems.</p><p>At issue is a <a href="https://www.tvtechnology.com/news/nab-urges-fcc-to-allow-software-based-eas">petition</a> from the NAB (<a href="https://www.fcc.gov/ecfs/document/1033123856452/1">PS Docket Nos. 15-94 & 22-329</a>), filed at the end of March, to fast-track its request to allow broadcasters to transition from hardware-based decoders to software for emergency alerting. The association is asking for urgent action in part because hardware supplier <a href="https://www.radioworld.com/news-and-business/business-and-law/sage-alerting-supports-nab-eas-petition">Sage Alerting Systems</a>, one of two hardware suppliers, has recently stopped production of devices and “the current legacy ecosystem is not sustainable.” </p><p>Digital Alert Systems, the other provider of hardware-based EAS systems to broadcasters, recently <a href="https://www.radioworld.com/news-and-business/business-and-law/digital-alert-systems-warns-of-risks-in-software-only-eas-proposal ">told</a> the FCC that it thought the proposal is premature and highlighted unresolved issues related to cybersecurity, regulatory compliance and operational challenges associated with software-only EAS platforms.</p><p>NCTA–The Internet & Television Association, the trade group representing major cable operators, said “commendable steps” have been taken in recent years to upgrade  alerting systems, including the use of the Common Alerting Protocol (CAP), a technology that helps improve clarity and provide more detail about emergency alerts. </p><p>“NAB’s proposal to permit EAS Participants to elect software-based EAS solutions may present the Commission with another opportunity to ensure that emergency alerting keeps pace with modern technology,” NCTA said in its filing. “Although NAB’s proposal discusses the use of a software-based EAS encoder/decoder in the context of broadcast station operations, such a solution may be of use to cable EAS participants as well.</p><p>“NCTA agrees with NAB that any such solution should not be directly exposed to the internet or be fully cloud-based," the association added. "This approach would be consistent with other software-based aspects of broadcast and cable network operations. NCTA also agrees that consideration of this issue is made more necessary by Sage Alerting Systems’ decision to cease production of its encoder/decoder device.”</p><p>NAB’s proposal has drawn support from <a href="https://www.tvtechnology.com/news/sbe-supports-nab-proposals-for-eas-rule-changes">SBE</a>.</p> ]]></dc:content>
                                                                                                                                            <link>https://www.tvtechnology.com/news/cable-industry-backs-broadcasters-move-to-software-based-eas</link>
                                                                            <description>
                            <![CDATA[ Proposal ‘presents the Commission with another opportunity to ensure that emergency alerting keeps pace with modern technology’ ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">Dp6M7dvz9xgbPiqZPMadFC</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/Vi25hASYhrcjY83ApdGusE-1280-80.png" type="image/png" length="0"></enclosure>
                                                                        <pubDate>Thu, 08 May 2025 13:42:08 +0000</pubDate>                                                                                                                                <updated>Thu, 08 May 2025 16:35:27 +0000</updated>
                                                                                                                                            <category><![CDATA[Business]]></category>
                                                                                                <author><![CDATA[ tom.butts@futurenet.com (Tom Butts) ]]></author>                    <dc:creator><![CDATA[ Tom Butts ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/Ym75XZxKuaGiZGj7nMGeGM-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                <media:content type="image/png" url="https://cdn.mos.cms.futurecdn.net/Vi25hASYhrcjY83ApdGusE-1280-80.png">
                                                            <media:credit><![CDATA[Creative Commons]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[EAS]]></media:description>                                                            <media:text><![CDATA[EAS]]></media:text>
                                <media:title type="plain"><![CDATA[EAS]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/Vi25hASYhrcjY83ApdGusE-1280-80.png" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>The cable industry has <a href="https://www.fcc.gov/ecfs/document/105021871028974/1">told</a> the Federal Communications Commission it supports the National Association of Broadcasters’ proposal to allow broadcasters to use software-based Emergency Alert Systems.</p><p>At issue is a <a href="https://www.tvtechnology.com/news/nab-urges-fcc-to-allow-software-based-eas">petition</a> from the NAB (<a href="https://www.fcc.gov/ecfs/document/1033123856452/1">PS Docket Nos. 15-94 & 22-329</a>), filed at the end of March, to fast-track its request to allow broadcasters to transition from hardware-based decoders to software for emergency alerting. The association is asking for urgent action in part because hardware supplier <a href="https://www.radioworld.com/news-and-business/business-and-law/sage-alerting-supports-nab-eas-petition">Sage Alerting Systems</a>, one of two hardware suppliers, has recently stopped production of devices and “the current legacy ecosystem is not sustainable.” </p><p>Digital Alert Systems, the other provider of hardware-based EAS systems to broadcasters, recently <a href="https://www.radioworld.com/news-and-business/business-and-law/digital-alert-systems-warns-of-risks-in-software-only-eas-proposal ">told</a> the FCC that it thought the proposal is premature and highlighted unresolved issues related to cybersecurity, regulatory compliance and operational challenges associated with software-only EAS platforms.</p><p>NCTA–The Internet & Television Association, the trade group representing major cable operators, said “commendable steps” have been taken in recent years to upgrade  alerting systems, including the use of the Common Alerting Protocol (CAP), a technology that helps improve clarity and provide more detail about emergency alerts. </p><p>“NAB’s proposal to permit EAS Participants to elect software-based EAS solutions may present the Commission with another opportunity to ensure that emergency alerting keeps pace with modern technology,” NCTA said in its filing. “Although NAB’s proposal discusses the use of a software-based EAS encoder/decoder in the context of broadcast station operations, such a solution may be of use to cable EAS participants as well.</p><p>“NCTA agrees with NAB that any such solution should not be directly exposed to the internet or be fully cloud-based," the association added. "This approach would be consistent with other software-based aspects of broadcast and cable network operations. NCTA also agrees that consideration of this issue is made more necessary by Sage Alerting Systems’ decision to cease production of its encoder/decoder device.”</p><p>NAB’s proposal has drawn support from <a href="https://www.tvtechnology.com/news/sbe-supports-nab-proposals-for-eas-rule-changes">SBE</a>.</p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Blue Alert Codes Can Now Be Used, Though Use is Voluntary ]]></title>
                                                                                                <dc:content><![CDATA[ <p><strong>WASHINGTON--</strong>This is the first full week that alert originators can begin to issue the new <a href="https://www.tvtechnology.com/tag/blue-alert">Blue Alert</a> event code. In January 2018, the Federal Communications Commission amended its rules regarding EAS and WEA emergency alert codes and voted to add a new code — known by its moniker B L U. This new alert can be used whenever there is imminent danger to a law enforcement officer, such as when an officer is injured, missing and in cases where there is fear of potential injury to law enforcement officers.</p><p>Although the new code is now on the books, it’s not mandatory that alert originators use it.</p><p>When the FCC moved to amend EAS rules in December 2017 by adding the new event code, the industry had mixed views on the necessity of such a decision. Many comments in the FCC’s ECFS database were critical, with one individual calling the move a “purely political sop” to police organizations, saying there’s no need for an EAS code that “nobody will use.”</p><p>The decision to add the code was led by the Department of Justice after two New York City Police detectives were killed in the line of duty in 2014. The new alert codes were put in place to help protect officers, said Chairman Ajit Pai at the time. “We owe [these detectives] and their brave family members who come here today a tremendous debt of gratitude,” Pai said. “[The] FCC attempts to do that today by adopting rules that police officers across America and the communities they so proudly serve will be better protected.”</p><p>The order states that state and local agencies have the option to send warnings to the public via EAS broadcast or through the Wireless Emergency Alert system to consumers’ wireless phones. As with Amber Alerts and weather alerts, usage of this code will be voluntary on a case by case basis.</p><p>The official go-date for the delivery of Blue Alerts over EAS was Jan. 18, 2019, and broadcast groups like the Alabama Broadcast Association (ABA) encouraged its members to begin to code their EAS equipment to include the Blue Alert. According to Sharon Tinsley, president of ABA, the state’s main law enforcement group, the Alabama Law Enforcement Agency, does plan to use the alerts when needed.</p><p>In response, EAS software manufacturers have been prepping. Digital Alert Systems DasDec users will be able to access the BLU event code as part of the company’s <a href="https://www.tvtechnology.com/equipment/das-monroe-electronics-announce-version-4-0-software">v4.0 software update</a>. Trilithic/Viavi includes the BLU event code in its v18.10 software update. Gorman-Redlich said it has a update, and requests that stations contact their office for details. Sage Endec users are being told that update firmware will be available this week.</p><p>Broadcasters and cable operators are also being asked to watch for additional information updates from their individual state emergency communication committees.</p><p>Under the order, state and local agencies have the option to send warnings to the public either through EAS broadcast or through the Wireless Emergency Alert system to consumers’ wireless phones. As with Amber Alerts and weather alerts, usage of this Blue Alert code will be voluntary on a case by case basis. </p> ]]></dc:content>
                                                                                                                                            <link>https://www.tvtechnology.com/news/blue-alert-codes-can-now-be-used-though-use-is-voluntary</link>
                                                                            <description>
                            <![CDATA[ New alert can be issued whenever imminent danger to law enforcement officers. ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">eNPcdw9c6kJtxrmZKMdaNK</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/AgzH8Cude2AQvnmtvnZuxi-1280-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Wed, 23 Jan 2019 18:49:33 +0000</pubDate>                                                                                                                                                                                                                                <category><![CDATA[FCC]]></category>
                                                    <category><![CDATA[Regulatory & Legal]]></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-320-70.jpeg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/AgzH8Cude2AQvnmtvnZuxi-1280-80.jpg">
                                                            <media:credit><![CDATA[null]]></media:credit>
                                                                                                                                                                                                                                                                                                                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/AgzH8Cude2AQvnmtvnZuxi-1280-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p><strong>WASHINGTON--</strong>This is the first full week that alert originators can begin to issue the new <a href="https://www.tvtechnology.com/tag/blue-alert">Blue Alert</a> event code. In January 2018, the Federal Communications Commission amended its rules regarding EAS and WEA emergency alert codes and voted to add a new code — known by its moniker B L U. This new alert can be used whenever there is imminent danger to a law enforcement officer, such as when an officer is injured, missing and in cases where there is fear of potential injury to law enforcement officers.</p><p>Although the new code is now on the books, it’s not mandatory that alert originators use it.</p><p>When the FCC moved to amend EAS rules in December 2017 by adding the new event code, the industry had mixed views on the necessity of such a decision. Many comments in the FCC’s ECFS database were critical, with one individual calling the move a “purely political sop” to police organizations, saying there’s no need for an EAS code that “nobody will use.”</p><p>The decision to add the code was led by the Department of Justice after two New York City Police detectives were killed in the line of duty in 2014. The new alert codes were put in place to help protect officers, said Chairman Ajit Pai at the time. “We owe [these detectives] and their brave family members who come here today a tremendous debt of gratitude,” Pai said. “[The] FCC attempts to do that today by adopting rules that police officers across America and the communities they so proudly serve will be better protected.”</p><p>The order states that state and local agencies have the option to send warnings to the public via EAS broadcast or through the Wireless Emergency Alert system to consumers’ wireless phones. As with Amber Alerts and weather alerts, usage of this code will be voluntary on a case by case basis.</p><p>The official go-date for the delivery of Blue Alerts over EAS was Jan. 18, 2019, and broadcast groups like the Alabama Broadcast Association (ABA) encouraged its members to begin to code their EAS equipment to include the Blue Alert. According to Sharon Tinsley, president of ABA, the state’s main law enforcement group, the Alabama Law Enforcement Agency, does plan to use the alerts when needed.</p><p>In response, EAS software manufacturers have been prepping. Digital Alert Systems DasDec users will be able to access the BLU event code as part of the company’s <a href="https://www.tvtechnology.com/equipment/das-monroe-electronics-announce-version-4-0-software">v4.0 software update</a>. Trilithic/Viavi includes the BLU event code in its v18.10 software update. Gorman-Redlich said it has a update, and requests that stations contact their office for details. Sage Endec users are being told that update firmware will be available this week.</p><p>Broadcasters and cable operators are also being asked to watch for additional information updates from their individual state emergency communication committees.</p><p>Under the order, state and local agencies have the option to send warnings to the public either through EAS broadcast or through the Wireless Emergency Alert system to consumers’ wireless phones. As with Amber Alerts and weather alerts, usage of this Blue Alert code will be voluntary on a case by case basis. </p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
            </channel>
</rss>