Web 2.0 "critical" to church, says Anglican CIO

Web 2.0 "critical" to church, says Anglican CIO

Summary: Web 2.0 is critical to the Anglican church if it is to keep up with today's youth, according to the Sydney diocese's CIO.

SHARE:
TOPICS: CXO, Enterprise 2.0
4

Web 2.0 is critical to the Anglican church if it is to keep up with today's youth, according to the Sydney diocese's CIO.

"The church is investing heavily in Web 2.0 technologies," CIO George Lymbers told IDC's Directions 08 event yesterday in Sydney.

Lymbers said developing tools which automatically protect users' data is important, saying that today's youth don't understand how to use Web 2.0 tools in a security-conscious way. "We want to protect them, and in doing so protect the reputation of the church," he said.

Web 2.0 also helps with the spread of the churches holdings: "We have thousands and thousands of properties," he said, adding that the church uses Google maps to link into databases to keep track of them.

However, the expanse of the Sydney diocese — over 2,000 sites "spread all over the place" — makes implementation of Web 2.0 difficult according to Lymbers, who says the extent of collaboration between sites depends on how much organisations are willing to pay for a connection.

"Telcos drive me crazy," he said, adding that they always promise to help minimise costs but the organisation is "led down the garden path more often than not".

Topics: CXO, Enterprise 2.0

Suzanne Tindal

About Suzanne Tindal

Suzanne Tindal cut her teeth at ZDNet.com.au as the site's telecommunications reporter, a role that saw her break some of the biggest stories associated with the National Broadband Network process. She then turned her attention to all matters in government and corporate ICT circles. Now she's taking on the whole gamut as news editor for the site.

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Talkback

4 comments
Log in or register to join the discussion
  • Web 2 and Anglicans

    Danger - Anglicans - Danger!
    It is really up to social and ethical leaders such as the Anglican Church to warrant and guarantee - no less than that - that the systems they are developing and using provide the necessary levels of privacy and security expected by church members and society. Dear Anglicans - just look at the OWASP web site for the dangers and unresolved security holes in Web 2! At a minimum servers MUST implement labelled security, yes - "Secure LINUX" with RedHat Enterprise LINUX 5, SUN Solaris 10 with "Enhanced Security" and others. This has to be the MINIMUM we can expect of such a Christian group - reasonable and caring protection of privacy with levels of system security regarded as being the "best of class" in the ICT sector.
    anonymous
  • Oh God..

    Most SQL injection attacks take place on Unix (derivitives) powered servers. That is just one of many types of attack that take place on interactive websites.

    How often does Bigpond or NineMSN get attacked and/or privacy breached? Both those sites run Windows and IIS.
    anonymous
  • Get the facts right...

    Do you do web dev? You should know that SQL injections are usually exploited because the coder forgot to put the appropriate protection on his code. Bigpond/NineMSN don't suffer from this because they obviously take care with their code - as you would hope happens with such large websites.

    So, it come down to the protection on the website code, not the server, as far as most SQL attacks go.
    anonymous
  • SQL Injection

    Yes - and I agree SQL injection is one of the ten OWASP problems.
    Now - do you remember "Trusted Oracle" - even with SQL injection occurring at the client end imagine the possibility that a "profile" at the row/column level at the server end enabled a process to be labelled against a particular DB instance - all possible with a modern LSPP based OS/DB combination that gives this support against application failure particular an interpreted app - like an AJAX style scheme operating on a client PC.
    That recognition of application code failure was what MULTICS was all about - at least at the higher file level. A modern "FMAC" labelled system - yes - not perfect - enables a better level of security to be created in database oriented systems, particularly where sensitive personal data may be involved..
    and remember, no application can be any more secure than the libraries it calls and compiler/interpreter it is based upon or the OS structures that they all use.
    OR - from a risk viewpoint - why choose an SQL structure at all for sensitive personal databases?
    Much safer ways to go! A far more responsible approach.
    anonymous