” Not in possession of …documents…[SIC: False] “

ballotOn the account of the Chicago Board of Elections, they had sent me a response by mail, only to be mailed to an undeliverable non-existent address: 4943 N. Lawler, which circumstantially upon verbal confirmation of the Jefferson Park Post Office Traffic manager: “We have no record.”


Upon providing the Board’s lawyer proof that they are required to maintain and preserve audit logs for auditing purposes the CBEC quickly moved and without written response sent my lawyer an optical disc and cover letter with some audit data via courier service in response to my evidence set forth:

Court Case: 15 CH 17495:

1.) In the 2002 (Active) Federal Election Commission document specifications for voting machines (Voting System Standards Vol. 1, PDF available upon request), all audit logs are required to be preserved and have date-time stamp in the log, as the guideline reads:

Sec: System Audit Purpose and Context

“Election audit trails provide the supporting documentation for verifying the correctness of reported election results. They present a concrete, indestructible archival record of all system activity related to the vote tally, and are essential for public confidence in the accuracy of the tally, for recounts, and for evidence in the event of criminal or civil litigation.”

And furthermore under sec: of Operational Requirements:

“The timing and sequence of audit record entries is as important as the data contained in the record. All voting systems shall meet the following requirements for time, sequence and preservation of the audit records:…

c. All audit record entries shall include the time-and-date stamp.”

2.) 2013 Contract Proposal for equipment by Dominion Voting Systems for Chicago Board of Elections, Cook County Board et al. Reference Audit Requirements table H-10:

On page 192 of the document under H “Misc. Requirements,” required ID “H-10″ and of which equipment is compliant reads:

“Incorporate a real time clock as part of the system hardware and all audit log record entries shall include a date/time stamp.”
Compliant equipment:
“The Dominion Voting Democracy Suite Electronic Management System (EMS), ImageCast Evolution (ICE), and the ImageCast Central (ICC) are all fully compliant with this requirement.”

Under the assurance and confidence that as it is Federally required per the 2002 (Voting System Standards Vol. 1) and admissibly compliant by the proposed 2013 contract for ballot equipment, the Chicago Board of Elections does, or is required to have record of the time-stamps of ballot casts, regardless of equipment used: Dominion, Sequoia or otherwise post 2002 FEC compliant equipment.

1.) Source: “http://www.eac.gov/…/Voting%20System%20Standards…” retrieved Sunday Jan 10th 2016, 1:51pm CST
2.) Source: “http://www.sos.state.co.us/…/DominionVotingSystemsColor…” retrieved Saturday Jan 9th 2016, 8:14pm CST

The CBEC finally released some data: all pre-election audit logs that contain only the testing and maintenance leading up to Election Day: [offer1]

We will report our initial findings of digital forensic admissibility with pre-election audit logs sometime after tomorrow, however our tests are circumstantial and would inevitably fail admissibility tests, so much we are confined that:

It implies from the cover letter that the CBEC maybe willing to provide us the complete audit logs if we can provide some evidence of admissibility in our methods.

However contrary to a predicted negative admissibility I would argue that the nature of beta testing and setup of ballot machine audit logs is of an entirely different nature than the chaotic (non random) occurrence of ballot casts, in that the former is from command (control/ Man nature) and the latter is through serendipitous (non-controlled) occurrence (God nature.)

I had asked for ballot cast time stamps, what I got was all the testing and maintenance audit logs prior to election day.

FOIA request to Chicago Board of Elections goes to deaf ears…

On March 23rd 2015 Jason Page, the founder of Benford Bench submitted a FOIA request to the FOIA department of the Chicago Board of Elections and since now have not received a response.  It is the data requested in the FOIA request that Jason believes would be critical to demonstrate the admissibility of Benford’s Law in the time each ballot is cast by machine during the election day; particularly a good control data we we hope is un-contrived is the 48 ward municipal election ballot data in Chicago for the 2015 mayoral election.

On July 29th 2015 Jason wrote a followup email to the FOIA department of the Chicago Election Board and waited five days for a response.  There is still no response to date.

We are doing our part looking at our options for the most effective path towards ensuring a fair and open 2016 Presidential Election. If you would like to help, the only requirement is of being direct relation of trust to anyone on our board or a mutual contact of trust.

Original FOIA request:

Introducing our new team member, Michael Fiedler

Michael Fiedler came to multikulti looking to volunteer his database skills, have an objective to learn PHP and socialize with people of similar “geeking.”

At Benfordbench he is developing a database structure for housing data that comes in from the Benford program, write php script for deploying that data into the database and a php script that will allow people to query the database and display results based on the query.

Jason has found a way to securely ftp files to the Benfordbench website and the thought perhaps is to have a cron check a folder where the uploaded files sit and process them into the database if they exist.

Jason is also working on a way to save the Benford graph results to a bitmap and send that with the report and link it in the database, perhaps also finding a way to convert the bmp to a web friendly format such as a gif.

Michael is eager to learn the PHP, as much as I am eager to learn from him.

Version 2.0 under development: Interfaces with BenfordBench.org

Version 2.0 will include the following new feature:

Data Reporter will include fields for investigation title, description, purpose of investigation, contact, data source details, probable cause and the data set, both original and normalized. The Data Reporter file can then be submitted to be published on BenfordBench.org, complete with graph and ability to output to PDF and share across email and social networking sites.