<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xml:base="https://www.webmaster-forums.net/crss/node/1034588" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title></title>
    <link>https://www.webmaster-forums.net/crss/node/1034588</link>
    <description></description>
    <language>en</language>
          <item>
    <title></title>
    <link>https://www.webmaster-forums.net/webmasters-corner/using-joomla-government-website#comment-1201140</link>
    <description> &lt;p&gt;great advice abishek, I appreciate all the feedback !!&lt;/p&gt;
&lt;p&gt;Cheers&lt;br /&gt;
iTchy&lt;/p&gt;
 </description>
     <pubDate>Wed, 31 May 2006 20:23:56 +0000</pubDate>
 <dc:creator>itchy</dc:creator>
 <guid isPermaLink="false">comment 1201140 at https://www.webmaster-forums.net</guid>
  </item>
  <item>
    <title></title>
    <link>https://www.webmaster-forums.net/webmasters-corner/using-joomla-government-website#comment-1201075</link>
    <description> &lt;p&gt;You&#039;ll want to carefully consider a decision in these circumstances.&lt;/p&gt;
&lt;p&gt;I expect most governments in developed countries have some sort of protocol in making decisions with regard to IT security.  New Zealand, for example, has a manual of guidelines (&lt;a href=&quot;http://www.security.govt.nz/sigs/index.html&quot; class=&quot;bb-url&quot;&gt;SIGS&lt;/a&gt;).  Though I&#039;m not well-versed with it, I&#039;d imagine there are processes involved such as conducting a security survey along with a viability study that may be satisfied.&lt;/p&gt;
&lt;p&gt;NZ also has an &lt;a href=&quot;http://www.e.govt.nz/&quot; class=&quot;bb-url&quot;&gt;e-govt&lt;/a&gt; initiative where policies on &lt;a href=&quot;http://www.e.govt.nz/policy/open-source/&quot; class=&quot;bb-url&quot;&gt;open source&lt;/a&gt; and &lt;a href=&quot;http://www.e.govt.nz/policy/trust-security&quot; class=&quot;bb-url&quot;&gt;trust and security&lt;/a&gt; are set out.  The &lt;a href=&quot;http://www.e.govt.nz/about-egovt/programme/checklist-2005/&quot; class=&quot;bb-url&quot;&gt;checklist&lt;/a&gt; treats security as &#039;mandatory&#039;.&lt;/p&gt;
&lt;p&gt;I&#039;m not sure if all that is relevant or not, as NZ is just one example.  Look up similar documentation that applies for the government you&#039;re working with.&lt;/p&gt;
&lt;p&gt;As a base line, the previous advice given in the thread is good common sense.  If the system you&#039;re building carries out important business processes, then you&#039;ll want to protect it as much as is feasible.  If it&#039;s just for presenting less important data, then a simple approach to security could be considered.&lt;/p&gt;
&lt;p&gt;Whether simply being open source presents an increased risk, I think is moot.  I just can&#039;t see free or open source software being inherently less secure.  The more visible a security hole is in the code, the sooner it gets patched.  Of course, this can vary from project to project (as with proprietary software), so if you think Joomla is not secure enough &lt;em&gt;by its own merit&lt;/em&gt;, then you might not want to risk it.&lt;/p&gt;
&lt;p&gt;In any case, I expect you&#039;ll have to meet some sort of legal standards and guidelines with it being a government website, so it&#039;s best to consult someone who can advise you about it.  Discuss it with the agency and follow it up with whatever department is responsible for that sort of thing.&lt;/p&gt;
&lt;p&gt;Disclaimer: I am not a lawyer. The above is opinion, not legal advice, etc etc. &lt;img src=&quot;https://www.webmaster-forums.net/misc/smileys/smile.png&quot; title=&quot;Smiling&quot; alt=&quot;Smiling&quot; class=&quot;smiley-content&quot; /&gt;&lt;/p&gt;
 </description>
     <pubDate>Wed, 31 May 2006 06:59:49 +0000</pubDate>
 <dc:creator>Abhishek Reddy</dc:creator>
 <guid isPermaLink="false">comment 1201075 at https://www.webmaster-forums.net</guid>
  </item>
  <item>
    <title></title>
    <link>https://www.webmaster-forums.net/webmasters-corner/using-joomla-government-website#comment-1201072</link>
    <description> &lt;p&gt;I mean if you use it for example with payment systems then the security is an issue, although any good script will be eventually hacked, it is best if you always upgrade the version of the script/software you have and always backup your site, thats the only way to deter hackers... even if I suggest a different CMS (content management system) its not 100% that it will remain secure...&lt;/p&gt;
 </description>
     <pubDate>Wed, 31 May 2006 03:08:20 +0000</pubDate>
 <dc:creator>demonhale</dc:creator>
 <guid isPermaLink="false">comment 1201072 at https://www.webmaster-forums.net</guid>
  </item>
  <item>
    <title></title>
    <link>https://www.webmaster-forums.net/webmasters-corner/using-joomla-government-website#comment-1201071</link>
    <description> &lt;p&gt;hi there,&lt;/p&gt;
&lt;p&gt;Thanks for your reply - much appreciated.&lt;/p&gt;
&lt;p&gt;How do you define &quot;other information&quot;.  I have been to the Joomla website and have post after post of people who have had their joomla sites hacked including some 1.0.8 versions.&lt;/p&gt;
&lt;p&gt;Sorry to drone but am very anxious about this.&lt;/p&gt;
 </description>
     <pubDate>Wed, 31 May 2006 02:50:23 +0000</pubDate>
 <dc:creator>itchy</dc:creator>
 <guid isPermaLink="false">comment 1201071 at https://www.webmaster-forums.net</guid>
  </item>
  <item>
    <title></title>
    <link>https://www.webmaster-forums.net/webmasters-corner/using-joomla-government-website#comment-1201070</link>
    <description> &lt;p&gt;My thoughts are, if your using joomla for puposes other than displaying information then there is this risk in security. But if youre planning to use joomla just for displayin stats, pictures, current events, and any other purely content related, then its a good way to use joomla to ease the maintenance of the site...&lt;/p&gt;
 </description>
     <pubDate>Wed, 31 May 2006 02:38:12 +0000</pubDate>
 <dc:creator>demonhale</dc:creator>
 <guid isPermaLink="false">comment 1201070 at https://www.webmaster-forums.net</guid>
  </item>
  </channel>
</rss>
