15.12.2012 Views

Project Requirements - Archaeological Survey of India

Project Requirements - Archaeological Survey of India

Project Requirements - Archaeological Survey of India

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Request for Proposal for establishing e-Governance Systems<br />

8.2 System Security <strong>Requirements</strong><br />

development <strong>of</strong> a system based on previously developed<br />

government accounts s<strong>of</strong>tware, and customization to the needs <strong>of</strong><br />

ASI. Implementation is expected to be completed within 6 months<br />

from the date <strong>of</strong> selection <strong>of</strong> the SI.<br />

It is expected that the solution implemented by the SI will be run in<br />

parallel with the existing systems for a period <strong>of</strong> at least 6 months in<br />

order to ensure that the output is the same in either case. The SI<br />

will also be required to migrate data from the existing systems to the<br />

new systems.<br />

8.2.1 Security features should be compliant withthe e-Governance Security Standards<br />

Framework.<br />

8.2.2 All systems should have integrated security features that areconfigurable by the<br />

system administrator tocontrol access to the application, functionalmodules,<br />

transactions, and data.<br />

8.2.3 Public key verificationmethods should be followed for verifying that the contents<br />

<strong>of</strong> a document have not been tampered with, and allowing the receiver to confirm<br />

the identity <strong>of</strong> the sender.<br />

8.2.4 The applications should require theuse <strong>of</strong> unique user IDs and passwords<br />

forauthentication purposes.<br />

8.2.5 The application should allow for the following:<br />

a. the enforcement <strong>of</strong> password standards<br />

b. the establishment <strong>of</strong> a specified periodfor password expiration, and<br />

c. the prohibition <strong>of</strong> recent passwordreuse<br />

8.2.6 System administrator should be able to define functional access rights and data<br />

access rights byassigned user ID, functional role, andowner organization.<br />

8.2.7 The systems should permit thesystem administrator to assign multiplelevels <strong>of</strong><br />

approval to a single user.<br />

8.2.8 System administrator should be able to restrict access tosensitive data elementsby<br />

named user, groups <strong>of</strong> users, orfunctional role.<br />

8.2.9 System should have audit logging capability to record accessactivity, including the<br />

following:<br />

RFP Volume 1:<strong>Project</strong> <strong>Requirements</strong> P a g e | 39

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!