The Rapid Architecture-Based Election Technology Verification (RABET-VTM) program is a rapid, reliable, and cost-effective approach to verifying non-voting election systems.
RABET-V is designed to introduce testing standards by which election offices can better understand the security, reliability, and risks associated with the technology used for non-voting systems like electronic pollbooks and election night reporting systems.
There is no standard, national-level process for verifying that non-voting election technology is secure, reliable, accessible, and usable. This puts elections jurisdictions at risk, burdens vendors with extra costs, and risks inconsistent and insecure outcomes.
RABET-V is a flexible, rapid, and cost-effective process for verifying vendor-provided and homegrown non-voting election technology. RABET-V assesses a product and the organization responsible for developing it by scoring its development process, architecture, and the product's performance to form a more complete picture of non-voting election technology.
For more details, please see our technical documentation.
There is no standard, national-level process for verifying that non-voting election technology is secure, reliable, accessible, and usable. This puts elections jurisdictions at risk, burdens vendors with extra costs, and risks inconsistent and insecure outcomes.
RABET-V is a flexible, rapid, and cost-effective process for verifying vendor-provided and homegrown non-voting election technology. RABET-V assesses a product and the organization responsible for developing it by scoring its development process, architecture, and the product's performance to form a more complete picture of non-voting election technology.
For more details, please see our technical documentation.
Traditional Testing Approach | RABET-V Holistic Assessment |
Struggles to keep pace with technology changes demanded by a continually changing threat environment. | Risk-based approach that is compatible with incremental changes. |
Evaluates the product in isolation. | Evaluates the product in the context of the organization and the environment in which it is developed. |
Accepts limited de minimis changes. Otherwise, requires full re-testing. | Scales to accept a variety of change types, from de minimis to full architecture changes. |
Incurs fixed costs on a regular basis for verification. | Can dramatically lower cost over time. |
Saves little to no time with reverification. | Facilitates re-verification in as little as hours depending on the maturity scores and the risk of the change. |
Incentivizes large, infrequent changes, reducing responsiveness to an evolving threat environment. | Incentivizes continual improvement and incremental changes by simplifying verification and rewarding security maturity. |
Typically requires redundant testing as part of the tailoring process. | Uses modularity by design and a simple delta-based approach to help meet specific state or local requirements, including for homegrown systems. |
Our two-page handout covers all the major distinctions of RABET-V and includes information on how you can help shape its future.
Learn MoreThis proposal lays out the intent to develop and conduct a RABET-V Pilot Program and evaluate the RABET-V process.
Read the ProposalThis documentation covers the goal and scope of the RABET-V program. It also discusses the core three activities and explores the role of the RABET-V Administrator.
Read the DocumentationThis document provides the process and requirements for attaining and maintaining status as an accredited assessor under the RABET-V program.
Read the DocumentIn the summary of our first pilot, we explain what a permanent operational program for RABET-V should look like, how it should be administered, and what it would take to run it.
Read the ReportWe provide an overview of the pilot process for RABET-V, including what lessons we learned and how we'll use them to make RABET-V a permanent fixture in the election community.
Read the Report