security requirements for e-government services: a methodological approach for developing a common...
TRANSCRIPT
Security requirements for e-government services: Security requirements for e-government services: a methodological approach for developing a methodological approach for developing
a common PKI-based security policya common PKI-based security policy
Authors:Authors: C. Lambrinoudakis, S. Gritzalis, F. Dridi, and G. PernulC. Lambrinoudakis, S. Gritzalis, F. Dridi, and G. PernulSource:Source: Computer Communications, 26(16), pp.1873-1883, 2003.Computer Communications, 26(16), pp.1873-1883, 2003.Adviser:Adviser: Min-Shiang HwangMin-Shiang HwangSpeaker:Speaker: Chun-Ta Li (Chun-Ta Li ( 李俊達李俊達 ))
22
OutlineOutline
• IntroductionIntroduction• The The e-governmente-government platform platform• Security issuesSecurity issues• The Public Key InfrastructureThe Public Key Infrastructure• A case-study: the A case-study: the e-governmente-government system Webocrat system Webocrat• ConclusionConclusion• CommentComment
33
IntroductionIntroduction
• e-governmente-government– Improving the quality of life, Disseminating knowledge, Improving the quality of life, Disseminating knowledge,
Generating earnings Generating earnings et al.et al.
• Information securityInformation security
• User privacyUser privacy
• Security measures – Risk analysis (Security measures – Risk analysis (RARA))– Assess the consequences from a potential security incidentAssess the consequences from a potential security incident
– Select the countermeasuresSelect the countermeasures
44
Introduction (cont.)Introduction (cont.)• RARA is to have precisely specified boundaries is to have precisely specified boundaries• e-governmente-government – amalgam of heterogeneous information – amalgam of heterogeneous information
systemsystem• A A frameworkframework can facilitate the development of a unified can facilitate the development of a unified
e-governmente-government security policysecurity policy– Isolated system Isolated system component of the e-government platform component of the e-government platform
• Organizational Framework for the Security RequiremenOrganizational Framework for the Security Requirements of e-government servicests of e-government services ((e-GOV-OFSRe-GOV-OFSR))
[Gritzalis and Lambrinoudakis, 2002[Gritzalis and Lambrinoudakis, 2002]]
55
The e-government platformThe e-government platform• [Wimmer and Traunmuller, 2002][Wimmer and Traunmuller, 2002]
UserUserUser … …
InternetInternet WirelessWireless
Governmental PortalGlobal Access Point
Local (state)Users
Local (state)Users
Central Server(NationalAuthority)
Remote Server(Local
Authority)
Remote Server(Local
Authority)
…
SUPPORTED SERVICES
66
Security issuesSecurity issues
• Identifying security requirementsIdentifying security requirements– e-Universitye-University– e-Votinge-Voting– Electronic collaboration of governmental departmentsElectronic collaboration of governmental departments– Web-based public servicesWeb-based public services
• Security requirementSecurity requirement– service phasesservice phases– actor typeactor type
77
Security issues (cont.)Security issues (cont.)• e-Universitye-University
88
Security issues (cont.)Security issues (cont.)• e-Votinge-Voting
99
Security issues (cont.)Security issues (cont.)• Electronic collaboration of governmental departmentsElectronic collaboration of governmental departments
1010
Security issues (cont.)Security issues (cont.)• Web-based public servicesWeb-based public services
1111
Security issues (cont.)Security issues (cont.)• A consolidated view of the security requirements for an A consolidated view of the security requirements for an
e-Government platforme-Government platform
1212
The Public Key InfrastructureThe Public Key Infrastructure
Registration
Digital signaturesEncryptionTime stamping
Non-repudiation
Key managementCertificatemanagementInformationrepository
Directory servicesCamouflagingcommunication
TTP to TTPinteroperability
Authorization
Audit
PKIservices
Use of PKI services for fulfilling e-government security requirements
Security requirements
Availability Performance Authentication LoggingManagementof privileges
Integrity Confidentiality Non-repudiation
Anonymity Publictrust
Untraceability Securestorage
a Not in the context of e-voting.
a
a a
1313
The Public Key Infrastructure The Public Key Infrastructure (cont.)(cont.)
• The hardware and software infrastructure The hardware and software infrastructure supporting the e-government portalsupporting the e-government portal– Risks:Risks:
• Unreliable hardware, Limited computing resources, Unreliable hardware, Limited computing resources, Unstable software, maintainability, Poor Unstable software, maintainability, Poor communication infrastructure communication infrastructure et al.et al.
– Countermeasures:Countermeasures:• Redundant servers, backup communication lines, Redundant servers, backup communication lines,
services contracts, testing procedures services contracts, testing procedures et al.et al.
1414
A case-study: the e-government syA case-study: the e-government system stem WebocratWebocrat
• e-GOV-OFSR framework e-GOV-OFSR framework WebocratWebocrat• Webocrat – implemented within the Webocrat – implemented within the Webocracy ProjectWebocracy Project• Protecting the system – PKI-based security architecture Protecting the system – PKI-based security architecture
((CSAPCSAP))– Communication (Communication (CC))
– Security (Security (SS))
– Authentication (Authentication (AA))
– Privacy (Privacy (PP))
1515
A case-study: the e-government syA case-study: the e-government system stem Webocrat Webocrat (cont.)(cont.)
• Webocracy project – EU funded research projecWebocracy project – EU funded research projectt
// Webocracy – Democracy on the Web// Webocracy – Democracy on the Web
ServiceOperator
ServiceCustomers
SystemAdministrator
KnowledgeManagement
KnowledgeManagement
DiscussionManagement
Opinion-Polling-Management
CSAP: Security Services
1616
A case-study: the e-government syA case-study: the e-government system stem Webocrat Webocrat (cont.)(cont.)
• actor typesactor types::– System administratorsSystem administrators
• Setting up the hardware/software infrastructureSetting up the hardware/software infrastructure
• Implemented the security services through the CSAP moduleImplemented the security services through the CSAP module
– Service operators (government employees)Service operators (government employees)• Setting up the Webocrat modulesSetting up the Webocrat modules
– Service customers (citizens, politicians)Service customers (citizens, politicians)• Accessing the system via well-specified “User Interfaces”Accessing the system via well-specified “User Interfaces”
• Citizens Information HelpdeskCitizens Information Helpdesk
1717
A case-study: the e-government syA case-study: the e-government system stem Webocrat Webocrat (cont.)(cont.)
• Webocrat-WebspaceWebocrat-Webspace– Publishing SpacePublishing Space
• Different types of documentsDifferent types of documents– Laws, Resolutions, Budgets Laws, Resolutions, Budgets et al.et al.
– Discussion SpaceDiscussion Space• Supporting intelligent communicationSupporting intelligent communication
– Inputs and comments – published in the Discussion spaceInputs and comments – published in the Discussion space
– Opinion Polling SpaceOpinion Polling Space• Electronic opinion polling on several issues/questionsElectronic opinion polling on several issues/questions
– Knowledge ManagementKnowledge Management
1818
A case-study: the e-government syA case-study: the e-government system stem Webocrat Webocrat (cont.)(cont.)• Security requirementsSecurity requirements & & risk analysisrisk analysis
1919
A case-study: the e-government syA case-study: the e-government system stem Webocrat Webocrat (cont.)(cont.)• CSAPCSAP security architecturesecurity architecture
Integrity, Confidentiality, Non-repudiation
Secure StorageLogging(Audit)
Access Control and Authorization(Management of Privileges)
Identification and Authentication
. Registration. Authorization. Key Management. Certificate Management. Directory Services. Time Stamping. Non-repudiation. Information. Repository. Audit
. Digital Signatures. Encryption. TTP to TTP. Interoperability. Camouflaging. Communication
2020
ConclusionsConclusions
• RA methodologies RA methodologies – Information system with well-defined boundariesInformation system with well-defined boundaries– Each information system must study independentlyEach information system must study independently– Consolidated list of requirementsConsolidated list of requirements
• e-GOV-OFSR frameworke-GOV-OFSR framework– service phasesservice phases– actor typesactor types
• PKI security servicesPKI security services
2121
CommentsComments
• Methodologies Methodologies requirements requirements existing existing approach approach framework (architecture) framework (architecture)
• RA RA each information system each information system framework framework
• PKI-based approach PKI-based approach other approach other approach– SecuritySecurity– EfficiencyEfficiency– Cost Cost