LogoLogo
  • Software Independence
  • System Security Architecture Description
    • Access Control
    • Artifact Authentication
      • Hashing of Continuously Exported Cast Vote Records
      • Preserving Voter Privacy
    • System Integrity
    • Networking
    • Password and Credential Policies
    • Defense-in-Depth and Least Privilege
    • Cryptography
  • Procedural and Operational Security
  • Known Vulnerabilities
  • Trusted Build
    • Build Machine Configuration
      • Installing Debian 12 to VxBuild
    • Online Phase
    • Offline Phase
    • Final Configuration
      • Secure Boot Signing
    • Installing an Image via vx-iso
      • Preparing USB Installation Drives
      • Installing a VotingWorks Image
      • Machine Configuration Wizard and VxCertifier
      • Verifying an installed image
    • Hash/Checksum Verification
    • Virt Manager - Network Access & Troubleshooting
  • Reliably Detectable Marks
Powered by GitBook
On this page
  • Invalid Marks
  • Valid Marks
Export as PDF

Reliably Detectable Marks

PreviousVirt Manager - Network Access & Troubleshooting

Last updated 1 year ago

This section maps to Requirement 1.2-B

Marks are determined valid and counted by the system if the amount of darker pixels in the bubble area exceeds a configurable threshold. This threshold can be adjusted to have a stricter or looser interpretation of what is considered a valid mark. The recommended and default threshold in the system is 7%, under which marks such as a light dot, a fold through a bubble, a stray mark outside of the bubble, or a small line just on the corner of a bubble will be considered invalid. Marks such as a completely filled bubble, half filled bubble, or an X in a bubble will be considered valid. Examples of invalid and valid marks along with the score for that mark (in green) are shown below.

Invalid Marks

Valid Marks