Rebecca Mercuri Security Checklist

From: Dennis Paull <dpaull_at_svpal_dot_org>
Date: Mon Aug 25 2003 - 00:12:45 CDT
Hi all,

Here is a document from Rebecca Mercuri listing security issues
she feels need to be addressed. It's not clear how many ought to
be addressed with the demo, probably most should be at least considered.



Generic Security Assessment Questions
Copyright 2000 by Rebecca Mercuri All Rights Reserved.
Certain generic questions emerge in the evaluation of secure products. These are not particular to the voting setting, but can be used as the basis of an assessment methodology for electronic vote tabulation systems. The list presented here can be augmented with additional items or finer detail, as necessary. Purchasers of secure systems should work with independent testing agencies that have demonstrated the high level of expertise necessary in order to evaluate vendor responses to these questions.
What are the assets that require security protection?
What security risks have been identified, and what is the likelihood of each?
What countermeasures have been specified to deal with the identified risks?
What security assurance level has been selected for the system? Justify the appropriateness of this rating. How has conformance been established?
What assumptions are made about the operating environment in order for it to be deemed secure?
What are the policies and rules required to enforce security?
What are the specified security functions and assurance measures? Have these been traced back to the functional requirements to insure that coverage is comprehensive?
Has a security requirements rationale document been presented? Does it demonstrate consistency with the security objectives for the system? Is the rationale comprehensive and consistent? Are any objectives unsatisfied, and if so, why?
What are the integrity concerns, and how have these been addressed?
What procedures are in place for secure system development? How have these been enforced and documented?
What are the resource allocation, priority of service, and fault tolerance policies and procedures?
What are the data requirements, and how are these implemented and enforced?
What are the data retention policies and procedures?
Have all communication paths been identified and secured as appropriate?
What are the confidentiality requirements, and how are these implemented and enforced?
What are the user roles? How are rules applied and enforced with the roles?
What are the authentication, authorization, and access control policies? How are these applied and enforced?
What are the administrative tasks and responsibilities?
Have the interfaces been assessed as to their appropriateness and correctness?
Are all administrator and user guidance documents complete and useable?
What are the startup, shutdown, recovery, and rollback policies? Which roles are responsible for these tasks?
How is the system delivered, installed, and generated? Which roles do this?
What tests are performed in order to insure correctness? When are these tests done? Who is responsible for conducting these tests?
How is the system validated for acceptance and compliance? Who does this?
What are the facility requirements, including physical protection of the system? What roles have been assigned responsibility for facility aspects?
Questions for Voting System Vendors
Copyright 2000 by Rebecca Mercuri All Rights Reserved.
The following questions can be used in conjunction with the generic security questions in order to elicit information regarding any electronic balloting and/or tabulation system under assessment. Answers should include thorough documentation and independent evaluation and testing to support vendor claims. Additional questions pertinent to the particular system being investigated should be added as necessary.
What means is used to separate voter identity from voted ballot?
How is the balloting process secured such that voter submissions can not be observed, or recorded in any way that is traceable to the individual voter?
What actions on the system are audited?
How is the auditing process precluded from associating voters with cast ballots?
How is the audit trail accessed and used?
Who is permitted to access the system (through all aspects of handling)?
What facilities are provided for recount purposes?
How are voters authenticated and authorized to cast ballots?
What access controls are in place to ensure single ballot per voter per election?
If multiple systems are deployed, how are voters tracked so the same person does not vote in different formats?
What controls are used to ensure that the correct ballot is provided to the voter?
What controls are provided to ensure that each ballot item is voted properly?
How are all forms of tampering detected and prevented?
How is vote confirmation provided without ballot-face receipt?
How is the voter prevented from retaining a copy of the cast ballot?
How does the system assure that each ballot has been correctly recorded?
How does the voter know that a cast ballot has been accepted?
How is vote tabulation correctness assured?
What features are employed to ensure operability of the voting system throughout the election?
How are downtimes handled in the event that they do occur?
What alternative balloting system is available for voters when the system is down?
How do the poll workers and system administrators know that the system is operating correctly?
How is the voting system precluded from use when deemed inoperable?
================================= = The content of this message, with the exception of any external = quotations under fair use, are released to the Public Domain ================================= Received on Sun Aug 31 23:17:15 2003

This archive was generated by hypermail 2.1.8 : Sun Aug 31 2003 - 23:17:18 CDT