About
Policies
Activities
Contacts
Register
Feedback
Glossary
Search
Home

CANRI Project Plans 2002-2003

Return to: [Project Plan Summaries]     [Project Plan Guidelines]     [Project Roles]

Project # 01-Access Management

Go to:    [Schedule & Costs]     [Deliverables]    [Organisational Chart]

[Back to top]

1 DOCUMENT CONTROL

1.1 Revision History

Version

Revision Date

Summary of Changes

1 28/6/02 First Draft
     
     
     
 

 

1.2 Distribution

This document has been distributed to:

Name

Position

Version

Date Issued

Lisa Harvey Authentication Consultant 1 28/06/02
Jonathan Doig CANRI Program Manager 1 28/06/02
       
 

 

1.3 Approvals

This document requires the following approvals:

Role

Name

Position

Approved (Initials)

Date Approved

Version Approved

Senior User CRG to appoint        
Senior Supplier Malcolm Morgan Manager Network Support, DLWC      
other…          
 

 

[Back to top]

2 Short name or acronym

Access Management

3 Abstract

Most CANRI resources are public access. Some datasets and applications require various levels of registration or access approval. The access management project provides within the CANRI Framework a mechanism for applications and datasets to be appropriately restricted to authenticated users. It also provides a mechanism for a user to have a single UserID and password for access all her authorised CANRI resources.

[Back to top]

4 Target audience

Primary audience:

State government

Secondary audience:

  • Farmers/Landcare
  • Local government
  • Students/academics
  • Environment/community groups
  • Industry

Main regional  audience:

  • Not applicable

Other comments:

[Back to top]

5 Participating organisations

5.1 Lead agency or organisation

5.2 Other agencies or organisations

OrganisationRole in projectContact name

Netegrity Inc

Supplier

Drew Cossar

OR

   

Computer Associates

Supplier

David Wall

Energetica

Consultant – adviser

Lisa Harvey

[Back to top]

6 Contacts

Author

  • Name: Lisa Harvey
  • Position: Authentication Project Consultant
  • Phone: 295859850
  • Fax: 295692072
  • Email: lisa@energetica.com.au
  • Organisation: Energetica Pty Ltd

Project manager

Project Steering Committee

Project sponsor

  • Name: Jonathan Doig
  • Position: CANRI Program Director
  • Phone: 298957781
  • Fax: 298957834
  • Email: jdoig@canri.nsw.gov.au
  • Organisation: CANRI

Senior supplier

  • Name: Malcolm Morgan
  • Position: Manager Network Support
  • Phone: 298957660
  • Fax:
  • Email: mmorgan@dlwc.nsw.gov.au
  • Organisation: DLWC

Senior user

  • Name: TBA
  • Position:
  • Phone:
  • Fax:
  • Email:
  • organisation:

[Back to top]

7 Project definition

7.1 Project description and objectives

Currently most data and applications provided within the CANRI framework are publicly accessible, with no restriction and few registration requirements. Where registration or user login is required this has been independently implemented in each application.

The current situation presents a number of weaknesses:

  1. Sharing sensitive data within the CANRI framework requires considerable effort on the part of the Data Custodian and the application builders. Data are either not served or it are expensive to serve.
  2. The levels of security development vary between applications.
  3. Duplication of development effort.
  4. Users with access to many restricted data and applications have to remember many UserIDs and passwords. This degrades the user experience, increases administration load, and adds a security risk as users will use weak passwords, or write them down.

 

The Access Management project will implement infrastructure that provides a central repository for usernames passwords and permissions that can be accessed by applications and datasets within the CANRI framework to ensure that the user making the request is properly authorised to do so. This system can be used by data custodians to build in authentication and authorisation into their applications or data. This has the following benefits:

  1. Enables agencies to more easily share sensitive information.
  2. Enables users to have a single UserID and password for access to all the data and applications within the CANRI framework for which they are registered and approved.
  3. Allows a variety of authorisation policies to suit data custodian requirements
  4. Facilitates stronger authentication in the future such as digital signatures, tokens or PKI.
  5. Reduces costs of implementing authentication in applications.
  6. Reduces the risks of weak application authentication design.

Simple administration, delegated administration, user self-registration and profile management.

7.2 Inclusions and exclusions

This project includes the establishment of the authentication service within the DLWC computing environment, and the design of a number of models for use by data and application custodians.

One pilot project will be implemented to evaluate the system, the technology, and assess its effectiveness. Assessment of the administration loads placed on DLWC and resource custodian staff is included in the pilot evaluation.

This project does not include the upgrade of data custodian web servers or application as required to implement authentication (other than the pilot project).

The project also includes finalisation of the draft strategy developed in the 2001-2002 Authentication consultancy.

7.3 Related initiatives and interdependencies

This project is dependent on the final outcomes of the 2001-2002 Authentication consultancy.

7.4 Technological environment

CA eTrust Access Control policy store will be located on one of DLWC’s Solaris web servers. It will access an eTrust Directory store.

OR

The Netegrity SiteMinder Policy Server will be located on one of DLWC’s Solaris web servers. It will access an existing directory store (iPlanet – free with Solaris 8; Netware e-Directory – existing).

Web agents will be installed (included in licence fees) on appropriate data custodian web sites.

Delegated management will allow access to the policy server by data custodians for administration.

7.5 Prerequisites and assumptions

A 500 user licence is sufficient for first year of operation.

DLWC infrastructure has the capacity for this implementation and are willing to contribute in-kind.

Agency chosen for Pilot will be willing to participate and contribute in-kind.

Vendors will be able to deliver to the requirements outlined in the 2001-2002 Authentication Consultancy.

[Back to top]

8 Deliverables

8.1 Details of deliverables

Click here to see list of deliverables in pdf format.

8.2 Environmental theme

  • Not applicable

8.3 Type of deliverables

  • Catalog
  • Operator
  • Network
  • Other
  • This project provides framework technology.

8.4 Additional information

[Back to top]

9 Schedule and costs

9.1 Schedule and cost details

Click here to see project schedule and costs in pdf format.

9.2 Additional information

LPI and OIT have expressed interest in the project. Possible synergies with existing OIT initiatives exist.

[Back to top]

10 Project organisation and controls

10.1 Organisation Chart

Click here to see organisation chart in pdf format.

10.2 Risk

Project or business risk

Proposed response

Performance - the installed system will not perform adequately to be of use to data custodians. Performance expectations will be well defined. Configuration options required to boost performance will be identified.
Custodian costs – the costs to custodians will be prohibitive. Value propositions will be defined. A variety of configurations will be offered to Custodians.
Security vulnerabilities – Security vulnerabilities will be discovered within the software or configuration. Security vulnerabilities will be monitored (eg bugtraq, vulnwatch). Patch updates to software should be applied as soon as they are available.
Hardware requirements – DLWC hardware is inadequate for managing the new service DLWC should do appropriate assessments in advance.
Administration Overheads – Administration loads added to the DLWC and custodians Good directory/policy design. Appropriate selection of options for custodians. Good documentation, delegated administration. Well-trained administrative staff.
Inadequate user licence estimates – 500 users may be inadequate Processes for funding custodian requirements will be identified in the Strategy. Costs for extra users will be identified.
Design and deployment consultancy will be underestimated. Keep the scope simple. Seek expertise from within OIT (for directory design). Obtain detailed estimates from suppliers before project begins. Perform risk analysis of project implementation.

10.3 Quality management

Progress reports will be provided to the CANRI coordination team every two months or otherwise as required.

The Project Manager (or a representative) will attend CANRI Program Implementation Group meetings to discuss progress on the project.

The Senior User (or a representative) will attend CANRI Community Reference Group (CRG) meetings or contact a member of the CRG prior to each meeting to enable discussion on progress of the project and to ensure that users needs are met.

Other quality management measures to be adopted:

[Back to top]

11 Other information

[Back to top]

12 Executive signoff

The Project and its outcomes are consistent with the business policies and strategies of this organisation as its sponsor. Resources are available to adequately supplement those provided by CANRI funding for the substantial delivery of expected project outcomes and for the realisation of described benefits.

This project plan has been prepared in accordance with the 2001/02 CANRI Project Plan guidelines

The project is consistent with the business policies and strategies of this agency as its sponsor. Resources are available to adequately supplement CANRI funding for the provision of the stated project deliverables and the realisation of stated objectives.

Signature:

 

Name:

 

Position:

 

Date:

 

[Back to top]

Return to: [Project Plan Summaries]     [Project Plan Guidelines]     [Project Roles]


Privacy
Copyright Disclaimer