Guilty! Arizona Senate Debunks The Left’s “Big Lie”

Irrefutable testimony from the Arizona Senate audit team debunks the left’s “big lie”. Arizona senators have been vindicated in their search for information on the 2020 election. Senate President Karen Fann and Senator Warren Petersen, Chairman of the Senate Committee on Judiciary presided over a hearing today on the progress of the unprecedented full forensic audit of the Maricopa county election. Cyber Ninjas CEO, Doug Logan who led the audit and Ben Cotton, founder of CyFIR testified about some of their findings. Ken Bennett, Senate Liaison for the audit, was also present. Fann opened with remarks, stating the “audit was not easy and has been a national, if not international event.”

The Senate audit was not about merely counting ballots. Over 1500 people were involved from all over the country and about 1100 of them were volunteers, according to Fann’s opening remarks. The independent auditors painstakingly combed through upwards of 2.1 million ballots. An audit with this level of detail has never been performed. The hearing opened with a detailed video accounting of the caution and care with which the audit was performed.

“a bipartisan effort with the intent to provide feedback to [voters] to enable them to get better in their election process or to provide findings to the Arizona Senate to enable them to create measures that would ensure that in the future that the residents of Arizona could have confidence in the election process.

To date, issues were found with the storage and labeling of ballots, record keeping, failure to do security updates, failure to provide system logs to the auditors, and a breach of public server with unauthorized access. It is now undeniably true that county officials failed to follow a myriad of rules regarding the proper conduct of free and fair elections. Unfortunately, the Maricopa County Board of Supervisors (MCBOS) has yet to deliver routers, passwords, and hardware keys previously subpoenaed by the Arizona State Senate.

Among the specifics discussed by Bennett and Logan, who talked about the chain of custody and ballot counting and security issues are the following. Starting on April 21 the following materials were received:

Once auditors received material, 1691 boxes of “mostly ballots” were received on 46 pallets.

8 boxes on the pallets that were not on the manifest and a “couple of boxes on manifests that were not present.”

Two boxes had data cards, hard drives, and fobs, all of which were transferred to Ben Cotton of CyFIR for data analysis.

Boxes had personally identifiable information (PII) interspersed with “spoiled ballots” and were segregated and secured immediately—those created another 16 new boxes.

9 high-volume scanner machines were received. 20 adjudication stations were received.

EMS (election management system) workstation and EMS servers along with some miscellaneous equipment were also received.

385 precinct tabulators were received on racks and each were identified and recorded by serial number.

24/7 Livestream cameras (two petabytes worth by the end) and strict chain of custody within view of a camera with a paper trail and two or more people of different political parties every time something was moved.

Bennett explained that there were significant issues with ballot batches being properly identified on the outside of the boxes. “Mostly from the voting centers” he continued, “There were around 1000 in a batch in some boxes.. and you would see a batch number on some…[but not others]…some had cut seals.” Batch counts were often not matching or poorly documented.

Did you see this tidbit?

"...Additionally, in March 2021 (four or five months AFTER the election) 37,646 queries hit the system for a “blank password on a system that only contained 8 accounts,” according to Cotton.

Cotton explained that “clearly, there was a script executed by an EMS admin.” He has no idea where that script came from. That is why he needs the router logs and Splunk data.

The system works on a FIFO basis, first in first out. This is a critical point because once the system hits 20 megabytes of information, the older information is deleted.

Therefore, as Petersen summarized, those 37,646 queries churned the data, so data is only available back to February of 2021..."

So.

For those who don't understand why this is direct evidence of fraud, let me explain why they did this:

There is only 20 MB of space available on the computer system for these crucial log files. That can always be changed and increased, but these systems probably didn't generate enough log entries under normal operation to saturate those files in a standard election process and cause the log file size to exceed 20 MB (just a guess).
If you get more than 20 MB of log files, system will "FIFO" out (First In, First Out) and chop the oldest text off of the log files so they can continue to write new data to the logs. There are many systems that will choke and cause errors if they cannot write to a log file if they are configured to do so, so many systems are configured this way.
Someone logged on who could run scripts as an administrator which would allow them to run without entering a password. NOTE: They likely had dozens if not hundreds of people who used the Administrator password, and it was probably known to people who they had no idea knew what it was. They may have even had it taped to the monitors for all I know (this happened in Antrim County, Michigan). This means they have no idea, none whatsoever who ran that script 37,646 times.
Whoever that person was repeatedly ran the script. Each time they ran the script, the act generated a log entry saying the script was being run with no password, and that the script was run.
As the script ran and generated a log file entry, it caused the log file to grow larger and larger in size until it reached 20 MB.
With each running of the script that generated a log file entry, it began to cut off the older log file entries, most likely the ones from before, during, and after November 3, 2020.
With each running of the script and the accompanying log file entry, any critical and important log file entries from the time surrounding the November 3rd election were chopped off and discarded.
Whoever the unknown and malicious "administrator" described above was had to repeat this script 37,646 times until they were satisfied no critical or damning log files remained from around the election window.

As someone who has had to personally inspect computers for malicious, intentional activity, the absence of logs (erased) or the manipulation of logs as described above is a GIANT RED FLAG that someone was trying to hide something and cover their tracks.

Of course, there may have been a valid reason someone ran a script all those times. But nobody knows why, what the script did exactly, where the script came from, and...most of all...who ran it.

IF THEY CAN GET THE ROUTER LOGS, THEY MAY WELL BE ABLE TO SEE WHERE THIS SCRIPT WAS BEING RUN FROM.

THEY CAN MATCH UP THE DATES AND TIMES THE SCRIPT WAS RUN WITH THE ROUTER LOG FILE DATES AND TIMES.

AND THAT MAY BE WHY THE PEOPLE RESPONSIBLE FOR THIS FRAUD ARE RESISTING WITH ALL THEIR MIGHT TO RELEASE THE ROUTER INFORMATION.

Notably, as known from previous discussions, the county does not have access to admin passwords. Only Dominion has access. CyFIR still needs admin passwords and hardware fobs. Cotton explained:

“If you as a county cannot validate independent of the vendor then how do you validate an election system that it is safe to vote? I would suggest, based on evidence Maricopa County does not have the ability to verify ems configuration independent of Dominion officials.”
Interesting because this is the case with the Fulton County PA assessment done by Wake TSI.. The dominion people ran the software because the county people weren’t trained or able to run the election software
https://drive.google.com/file/d/1VnJFxN3NdKQmcj2-8FDWMET8i__YlH7F/view?usp=sharing

Hope it helped to understand. There are a lot of technical issues, and I readily admit I am not up to speed on many of them, but I know computer malfeasance when I see it.

In my experience, any time you see logs missing or incomplete where they should be intact, it is almost always one of three things:

The system is not configured correctly to write logs appropriately.
Someone intentionally or unintentionally deleted them trying to fix an application or server problem.
Someone was trying to cover their tracks.

With someone mysterious logging in and running a script 37,646 times and nobody knows how or why, it is pretty clear to me that it is malfeasance. If it were legitimate, you can bet Dominion or the County would tell you the legitimate reason. They won't, because it is pretty clear to me, there is no legitimate reason.

I guarantee it: You won't see anyone step forward and try to justify it with "I was the one who ran that script, and..."

They won't do it, because that is a felony. It is a turd dropped on a sidewalk, and there won't be anyone owning up to it.

Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.