<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Business continuity and cybersecurity - which tail wags the dog? in Industry News</title>
    <link>https://community.isc2.org/t5/Industry-News/Business-continuity-and-cybersecurity-which-tail-wags-the-dog/m-p/20544#M2455</link>
    <description>&lt;P&gt;Yes I come from BC/DR background myself. When you talk security with some of those folk (not BCI or DRI particularly)m some of them get all prickly. &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 27 Mar 2019 20:59:43 GMT</pubDate>
    <dc:creator>j_M007</dc:creator>
    <dc:date>2019-03-27T20:59:43Z</dc:date>
    <item>
      <title>Business continuity and cybersecurity - which tail wags the dog?</title>
      <link>https://community.isc2.org/t5/Industry-News/Business-continuity-and-cybersecurity-which-tail-wags-the-dog/m-p/20537#M2452</link>
      <description>&lt;P&gt;Hello all.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The BC guys and gals often complain the security folks don't invite them to the party. Security folk complain about how BCP tries to be the directors in the crisis matrix. Nobody (particularly stakeholders and shareholders) wins when the bickering and dickering sours the matrix.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does anyone have experience or ideas they might share as to how we can 'all just get along'?&lt;/P&gt;</description>
      <pubDate>Mon, 09 Oct 2023 09:09:52 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Industry-News/Business-continuity-and-cybersecurity-which-tail-wags-the-dog/m-p/20537#M2452</guid>
      <dc:creator>j_M007</dc:creator>
      <dc:date>2023-10-09T09:09:52Z</dc:date>
    </item>
    <item>
      <title>Re: Business continuity and cybersecurity - which tail wags the dog?</title>
      <link>https://community.isc2.org/t5/Industry-News/Business-continuity-and-cybersecurity-which-tail-wags-the-dog/m-p/20539#M2453</link>
      <description>&amp;gt; j_M007 (Community Champion) posted a new topic in Industry News on 03-27-2019&lt;BR /&gt;&lt;BR /&gt;&amp;gt; &amp;nbsp; The BC guys and gals often complain the security folks don't&lt;BR /&gt;&amp;gt; invite them to the party. Security folk complain about how BCP tries to be the&lt;BR /&gt;&amp;gt; directors in the crisis matrix. Nobody (particularly stakeholders and&lt;BR /&gt;&amp;gt; shareholders) wins when the bickering and dickering sours the matrix. &amp;nbsp; Does&lt;BR /&gt;&amp;gt; anyone have experience or ideas they might share as to how we can 'all just get&lt;BR /&gt;&amp;gt; along'?&lt;BR /&gt;&lt;BR /&gt;I go to the BCI Forum meetings here in town, and invite them to all of ours ...&lt;BR /&gt;&lt;BR /&gt;====================== (quote inserted randomly by Pegasus Mailer)&lt;BR /&gt;rslade@vcn.bc.ca slade@victoria.tc.ca rslade@computercrime.org&lt;BR /&gt;Some folks are wise and some are otherwise. - Tobias Smollett&lt;BR /&gt;victoria.tc.ca/techrev/rms.htm &lt;A href="http://twitter.com/rslade" target="_blank"&gt;http://twitter.com/rslade&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://blogs.securiteam.com/index.php/archives/author/p1/" target="_blank"&gt;http://blogs.securiteam.com/index.php/archives/author/p1/&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://is.gd/RotlWB" target="_blank"&gt;https://is.gd/RotlWB&lt;/A&gt;</description>
      <pubDate>Wed, 27 Mar 2019 20:08:04 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Industry-News/Business-continuity-and-cybersecurity-which-tail-wags-the-dog/m-p/20539#M2453</guid>
      <dc:creator>rslade</dc:creator>
      <dc:date>2019-03-27T20:08:04Z</dc:date>
    </item>
    <item>
      <title>Re: Business continuity and cybersecurity - which tail wags the dog?</title>
      <link>https://community.isc2.org/t5/Industry-News/Business-continuity-and-cybersecurity-which-tail-wags-the-dog/m-p/20543#M2454</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.isc2.org/t5/user/viewprofilepage/user-id/1273539083"&gt;@j_M007&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;&lt;P&gt;Hello all.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The BC guys and gals often complain the security folks don't invite them to the party. Security folk complain about how BCP tries to be the directors in the crisis matrix. Nobody (particularly stakeholders and shareholders) wins when the bickering and dickering sours the matrix.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does anyone have experience or ideas they might share as to how we can 'all just get along'?&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;BR /&gt;Have to agree that the bickering can actually be very damaging to the organization, sometimes more so than an event.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Having lived through several events, I did the following:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1) Set up quarterly meetings to discuss issues and concepts between the groups (sometimes this had to be monthly &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt; )&lt;/P&gt;&lt;P&gt;2) Ensured that Security folk were invited to DR exercises (in my case they owned authentication and authorization, the firewalls, and the proxy servers)&lt;/P&gt;&lt;P&gt;3) Asked both teams to review all documentation&lt;/P&gt;&lt;P&gt;4) Developed a organization chart for DR exercises showing all reporting lines&lt;/P&gt;&lt;P&gt;5) Asked the CIO of the organization to notate who was the lead and approve 1 thru 4.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Really cut down on the bickering about who owned what.&amp;nbsp; Maybe I was lucky but this worked for me.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;d&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 27 Mar 2019 20:56:22 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Industry-News/Business-continuity-and-cybersecurity-which-tail-wags-the-dog/m-p/20543#M2454</guid>
      <dc:creator>dcontesti</dc:creator>
      <dc:date>2019-03-27T20:56:22Z</dc:date>
    </item>
    <item>
      <title>Re: Business continuity and cybersecurity - which tail wags the dog?</title>
      <link>https://community.isc2.org/t5/Industry-News/Business-continuity-and-cybersecurity-which-tail-wags-the-dog/m-p/20544#M2455</link>
      <description>&lt;P&gt;Yes I come from BC/DR background myself. When you talk security with some of those folk (not BCI or DRI particularly)m some of them get all prickly. &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 27 Mar 2019 20:59:43 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Industry-News/Business-continuity-and-cybersecurity-which-tail-wags-the-dog/m-p/20544#M2455</guid>
      <dc:creator>j_M007</dc:creator>
      <dc:date>2019-03-27T20:59:43Z</dc:date>
    </item>
    <item>
      <title>Re: Business continuity and cybersecurity - which tail wags the dog?</title>
      <link>https://community.isc2.org/t5/Industry-News/Business-continuity-and-cybersecurity-which-tail-wags-the-dog/m-p/20545#M2456</link>
      <description>&lt;P&gt;Yes get the C folks (CEO, COO, CFO) to put &lt;STRIKE&gt;there&lt;/STRIKE&gt;&amp;nbsp;their weight behind the CISO/CSO. CISO by the way is a humorous acronym for Francophone people, as it sounds like &lt;EM&gt;ciseaux&lt;/EM&gt; or scissors! &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 27 Mar 2019 21:06:25 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Industry-News/Business-continuity-and-cybersecurity-which-tail-wags-the-dog/m-p/20545#M2456</guid>
      <dc:creator>j_M007</dc:creator>
      <dc:date>2019-03-27T21:06:25Z</dc:date>
    </item>
    <item>
      <title>Re: Business continuity and cybersecurity - which tail wags the dog?</title>
      <link>https://community.isc2.org/t5/Industry-News/Business-continuity-and-cybersecurity-which-tail-wags-the-dog/m-p/20548#M2457</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.isc2.org/t5/user/viewprofilepage/user-id/1273539083"&gt;@j_M007&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;&lt;P&gt;Yes I come from BC/DR background myself. When you talk security with some of those folk (not BCI or DRI particularly)m some of them get all prickly. &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;Ah no say, it isn't so.......&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 28 Mar 2019 14:51:11 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Industry-News/Business-continuity-and-cybersecurity-which-tail-wags-the-dog/m-p/20548#M2457</guid>
      <dc:creator>dcontesti</dc:creator>
      <dc:date>2019-03-28T14:51:11Z</dc:date>
    </item>
    <item>
      <title>Re: Business continuity and cybersecurity - which tail wags the dog?</title>
      <link>https://community.isc2.org/t5/Industry-News/Business-continuity-and-cybersecurity-which-tail-wags-the-dog/m-p/20551#M2458</link>
      <description>&lt;P&gt;In my experience I've always found that developing a good relationship between the two "teams" before any incident applies bears most fruit. That way, the events that come to pass mostly strengthen both parties, and weeds out the weaknesses.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Of course, the attitudes of individuals can have great bearing, but I find as long as roles and responsibilities are clearly defined, as mentioned already, then there is little to bicker about.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Most importantly, it's important to take away the perceived "importance hierarchy" when nasty issues arise. Better to have a common goal, a consensus if you will, that allows objection provided it's constructive and sensible. After all, we are all working toward the same rough objectives - one likely fails to exist in its entirety without the other.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Mar 2019 11:38:45 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Industry-News/Business-continuity-and-cybersecurity-which-tail-wags-the-dog/m-p/20551#M2458</guid>
      <dc:creator>HTCPCP-TEA</dc:creator>
      <dc:date>2019-03-28T11:38:45Z</dc:date>
    </item>
    <item>
      <title>Re: Business continuity and cybersecurity - which tail wags the dog?</title>
      <link>https://community.isc2.org/t5/Industry-News/Business-continuity-and-cybersecurity-which-tail-wags-the-dog/m-p/20554#M2461</link>
      <description>&lt;P&gt;I'm glad to say that we don't have that problem.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Since the Cyber division is a sub division of the IT department, all BC issues are automatically planned with security in mind, and nothing moves forwards without our stamp of approval.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This doesn't mean that we are "the powers that will", but that everyone understands that to have better BC, you need to integrate with security, and we understand and push the fact that BC is an inherent aspect of securing the enterprise.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Win win all round.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Mar 2019 13:42:26 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Industry-News/Business-continuity-and-cybersecurity-which-tail-wags-the-dog/m-p/20554#M2461</guid>
      <dc:creator>MikeGlassman</dc:creator>
      <dc:date>2019-03-28T13:42:26Z</dc:date>
    </item>
    <item>
      <title>Re: Business continuity and cybersecurity - which tail wags the dog?</title>
      <link>https://community.isc2.org/t5/Industry-News/Business-continuity-and-cybersecurity-which-tail-wags-the-dog/m-p/20570#M2464</link>
      <description>&amp;gt; HTCPCP-TEA (Contributor I) posted a new reply in Industry News on 03-28-2019&lt;BR /&gt;&lt;BR /&gt;&amp;gt; In my experience I've always found that developing a good relationship between&lt;BR /&gt;&amp;gt; the two "teams" before any incident applies bears most fruit.&lt;BR /&gt;&lt;BR /&gt;I really don't understand why there are two "teams." BCP is (used to be) one of&lt;BR /&gt;the CISSP domains. One of my standard conference presentations is a two-hour&lt;BR /&gt;workshop on a one-page BCP tool. (I've got a very similar one on IRP.) I also&lt;BR /&gt;work (volunteer) in emergency management, and there is all kinds of crossover.&lt;BR /&gt;&lt;BR /&gt;====================== (quote inserted randomly by Pegasus Mailer)&lt;BR /&gt;rslade@vcn.bc.ca slade@victoria.tc.ca rslade@computercrime.org&lt;BR /&gt;Striving for excellence motivates you; striving for perfection is&lt;BR /&gt;demoralizing. - Harriet Braiker&lt;BR /&gt;victoria.tc.ca/techrev/rms.htm &lt;A href="http://twitter.com/rslade" target="_blank"&gt;http://twitter.com/rslade&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://blogs.securiteam.com/index.php/archives/author/p1/" target="_blank"&gt;http://blogs.securiteam.com/index.php/archives/author/p1/&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://is.gd/RotlWB" target="_blank"&gt;https://is.gd/RotlWB&lt;/A&gt;</description>
      <pubDate>Thu, 28 Mar 2019 17:18:04 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Industry-News/Business-continuity-and-cybersecurity-which-tail-wags-the-dog/m-p/20570#M2464</guid>
      <dc:creator>rslade</dc:creator>
      <dc:date>2019-03-28T17:18:04Z</dc:date>
    </item>
    <item>
      <title>Re: Business continuity and cybersecurity - which tail wags the dog?</title>
      <link>https://community.isc2.org/t5/Industry-News/Business-continuity-and-cybersecurity-which-tail-wags-the-dog/m-p/20571#M2465</link>
      <description>&lt;P&gt;Well BC and DR are two aspects of security to be sure. But the BC and the DR worlds (which are also discrete!) have many compliance and statutory bells and whistles to ring and tweet.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Why make things easy when you can complexify the fuzzification?&lt;/P&gt;</description>
      <pubDate>Thu, 28 Mar 2019 17:32:07 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Industry-News/Business-continuity-and-cybersecurity-which-tail-wags-the-dog/m-p/20571#M2465</guid>
      <dc:creator>j_M007</dc:creator>
      <dc:date>2019-03-28T17:32:07Z</dc:date>
    </item>
    <item>
      <title>Re: Business continuity and cybersecurity - which tail wags the dog?</title>
      <link>https://community.isc2.org/t5/Industry-News/Business-continuity-and-cybersecurity-which-tail-wags-the-dog/m-p/20572#M2466</link>
      <description>&amp;gt; j_M007 (Community Champion) posted a new reply in Industry News on 03-28-2019&lt;BR /&gt;&lt;BR /&gt;&amp;gt; Well BC and DR are two aspects of security to be sure. But the BC and the DR&lt;BR /&gt;&amp;gt; worlds (which are also discrete!) have many compliance and statutory bells and&lt;BR /&gt;&amp;gt; whistles to ring and tweet. &amp;nbsp; Why make things easy when you can complexify the&lt;BR /&gt;&amp;gt; fuzzification?&lt;BR /&gt;&lt;BR /&gt;Discretion (yes I know it's the wrong discreet) is the better part of ensuring the&lt;BR /&gt;enlargement of your corporate mini-empire. Yeah, I know BC is ensuring that&lt;BR /&gt;whatever happens *doesn't* interrupt your business, while DR is what you do&lt;BR /&gt;*after* your business has been interrupted, but so much of the analysis and so&lt;BR /&gt;many of the tools are the same that making a huge distinction between them is&lt;BR /&gt;another thing that drives me around the twist ...&lt;BR /&gt;&lt;BR /&gt;====================== (quote inserted randomly by Pegasus Mailer)&lt;BR /&gt;rslade@vcn.bc.ca slade@victoria.tc.ca rslade@computercrime.org&lt;BR /&gt;Great wits are sure to madness near allied. - John Dryden, 1681&lt;BR /&gt;victoria.tc.ca/techrev/rms.htm &lt;A href="http://twitter.com/rslade" target="_blank"&gt;http://twitter.com/rslade&lt;/A&gt;&lt;BR /&gt;&lt;A href="http://blogs.securiteam.com/index.php/archives/author/p1/" target="_blank"&gt;http://blogs.securiteam.com/index.php/archives/author/p1/&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://is.gd/RotlWB" target="_blank"&gt;https://is.gd/RotlWB&lt;/A&gt;</description>
      <pubDate>Thu, 28 Mar 2019 17:53:04 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Industry-News/Business-continuity-and-cybersecurity-which-tail-wags-the-dog/m-p/20572#M2466</guid>
      <dc:creator>rslade</dc:creator>
      <dc:date>2019-03-28T17:53:04Z</dc:date>
    </item>
    <item>
      <title>Re: Business continuity and cybersecurity - which tail wags the dog?</title>
      <link>https://community.isc2.org/t5/Industry-News/Business-continuity-and-cybersecurity-which-tail-wags-the-dog/m-p/20574#M2468</link>
      <description>&lt;P&gt;I like to look at business continuity and security globally in the context of ERM or ORM (organizational risk management).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There are so many little bits and pieces of threats and vulns that can bite you in the @$$ ets&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A BCP person can often broaden the scope of looking at the risks and work in conjunction with organizational security.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thankfully, the BCDR community are wising up to cyber threats, supply-chain threats, and reputational risk from catastrophes either wrought by humans or (super)natural forces and are trying to have playbooks supporting or working in tandem with information security.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, I still feel like the guy in Prufrock:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;&lt;EM&gt;For I have known them all already, known them all:&lt;/EM&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;EM&gt;Have known the evenings, mornings, afternoons,&lt;/EM&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;EM&gt;I have measured out my life with coffee spoons;&lt;/EM&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;EM&gt;I know the voices dying with a dying fall&lt;/EM&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;EM&gt;Beneath the music from a farther room.&lt;/EM&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;EM&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;So how should I presume?&lt;/EM&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;He knows how it's all going to go down! &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 28 Mar 2019 18:22:42 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Industry-News/Business-continuity-and-cybersecurity-which-tail-wags-the-dog/m-p/20574#M2468</guid>
      <dc:creator>j_M007</dc:creator>
      <dc:date>2019-03-28T18:22:42Z</dc:date>
    </item>
    <item>
      <title>Re: Business continuity and cybersecurity - which tail wags the dog?</title>
      <link>https://community.isc2.org/t5/Industry-News/Business-continuity-and-cybersecurity-which-tail-wags-the-dog/m-p/20597#M2473</link>
      <description>&lt;P&gt;I get you,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I don't understand why so many organisations have two teams rather than having it all in one either, but for whatever reason, that seems to be the norm these days.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But hey ho. I work with what I have in forn tof me, or try to change what's in front of me, given the chance.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 29 Mar 2019 13:52:32 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Industry-News/Business-continuity-and-cybersecurity-which-tail-wags-the-dog/m-p/20597#M2473</guid>
      <dc:creator>HTCPCP-TEA</dc:creator>
      <dc:date>2019-03-29T13:52:32Z</dc:date>
    </item>
  </channel>
</rss>

