Cannot believe I typed all that and TA crapped out. Here we go again.
Everything you need is in this thread and has been discussed and cited fully. If you are really interested in it, go back and read. I am betting, because you have only had this user name since July and started posting late on this thread, this is a sock. One created because your previous posting proved you to be a troll, or a shill only looking to gaslight the talking points.
Regardless, some bullet points you can start with:
MCBoE likes to hang their hat on transparency based on laughable "audits" by Pro V&V and SLI
https://www.maricopa.gov/DocumentCenter/View/66844/Post-Audit-Reporthttps://www.maricopa.gov/DocumentCenter/View/66843/SLI-Compliance-Forensic-Audit-Report?bidId=Pro V&V was a whopping 10 pages and they only tested 5 ICP2 devices. Even more laughable is even one of those was missing its security seal and their response was it "could have been missing for legitimate reasons" without actually finding out what that was. Their conclusion was BS as well
Quote:
Based on the results obtained during the Field Audit, Pro V&V determines the D-Suite 5.5-B Voting
System, on all evaluated components, is the voting system software and hardware certified for use in
Maricopa County and are the same as the software and hardware used in the conduction of the November 2020 General Election
Great legal speak for "well, everything we looked at was cool." Can't speak to the other 345 scanners and countless other pieces of hardware.
SLI was a bit more thorough, but laughable all the same. 35 ICP machines looked at, but hey, 5 didn't power on, 6 were missing their SIM cards, and one was a spare that wasn't actually used in the audit. No mention in either audit how these machines were selected and by who. Why also would a machines SIM or memory card be removed and used on another machine? Each machine is supposed to have its own, paired and serial numbered, to match the machine as stated by Dominions SOP documentation. SLI asked, MCBoE said, they moved them to another machine, and no follow up as to why/what happened to the others that were tied to those machines.
So ya, MCBoE is so obviously serious and transparent with the two companies who were charged with auditing their own work. That is right, Pro V&V / SLI were paid to setup the voting system. No conflict of interest there. Fox guarding the hen house and then floating softball questions to MCBoE with no follow up questions as to why.
As to a list of items in the CN audit where MCBoE did not comply or participate.
https://www.azsenaterepublicans.com/cyber-ninjas-reportVolume III
5.7.8 Missing subpoena items
5.7.12 January 12 and July 26 subpoena's for access to registration system and "records of authorized and unauthorized access" ignored. The county even replied they "were unaware of a breach" even though the MCBoE confirmed, in a media report December 4, 2020, voter information had been stolen.
6.2 not all log files retained for 22 months as required by law
6.4.1 EMS DB purged February 2nd, the day before the Pro V&V/SLI audits, , MCBoE chose not to respond at time of report when asked to explain the windows and EMS purges.
6.4.3 Corrupt ballot images 1.3 MM ballots scanned without issue prior to November 1. After November 1, 263,139 ballot images were scanned and completely unreadable. MCBoE was asked to provide new copies of these images, MCBoE didn't respond (no images provided and no explanation why not a single corrupted image happened before 11/1 but over 250k happened after.)
6.5.2 Multiple sections of findings regarding passwords, software patching, etc. not captured/mentioned in either Pro V&V/SLI audits.
6.4.3 List of subpoena items not provided by MCBoE
6.5.6.1.2 "14 days after Arizona Senate described the risk of evidentiary loss due to the continued use of election equiement, and 6 days after Judge Thompson ruled the subpoena neededd to be complied with." A user utilizing "emsadmin" login ran the infamous script to roll security logs. (1) what is it called when you delete data under subpoena? (2) if you have a legitimate reason, login to the device and clear the logs.