County elections security plan
- • submission of ballot information to Secretary of State
(1)(a) Each county clerk shall file a county elections security plan with the Secretary of State not later than:
(A) January 31 of each calendar year; and
(B) One business day after any revision is made to the county elections security plan.
(b) A county elections security plan shall include, but is not limited to:
(A) A written security agreement entered into with any vendor handling ballots;
(B) Security procedures for transporting ballots;
(C) Security procedures at official places of deposit for ballots;
(D) Security procedures for processing ballots;
(E) Security procedures governing election observers;
(F) Security procedures for ballots located in county elections work areas, buildings and storage areas;
(G) Security procedures for vote tally systems, including computer access to vote tally systems;
(H) The number and location of all video surveillance cameras within the elections office;
(I) Security procedures for scanning ballots into a vote tally system before the date of the election, if applicable; and
(J) Post-election ballot security.
(2) A security plan developed and filed under subsection (1) of this section is confidential and not subject to disclosure under ORS 192.311 (Definitions for ORS 192.311 to 192.478) to 192.478 (Exemption for Judicial Department).
(3) For each election, at the time the county clerk certifies the results of an election, the clerk shall submit to the Secretary of State a record of:
(a) The number of ballot envelopes received.
(b) The number of ballot envelopes accepted.
(c) The number of ballot envelopes not accepted.
(d) The number of ballot envelopes rejected.
(e) The number of tallied ballots.
(4) A county clerk may not scan ballots as described in ORS 254.478 (Preparation for counting ballots) unless the Secretary of State reviews and approves a security plan described in subsection (1) of this section. [2001 c.965 §48; 2009 c.592 §2; 2013 c.679 §1]
3 OregonLaws.org assembles these lists by analyzing references between Sections. Each listed item refers back to the current Section in its own text. The result reveals relationships in the code that may not have otherwise been apparent.