Posted on 07/15/2021 7:12:35 PM PDT by E. Pluribus Unum
Teams conducting a forensic audit in Arizona’s largest county said on July 15 that they want more items to complete their review, which has turned up several major discrepancies.
The auditors, led by Florida-based Cyber Ninjas, want ballot envelope images, router images, splunk logs, hard drives that contain information about the 2020 election in Maricopa County, and details on the county’s policies and procedures as they try to complete a review that started nearly three months ago.
That information could help clear up issues that have been identified.
Doug Logan, CEO of Cyber Ninjas, told senators at the Arizona state Capitol during a hearing that auditors could find no record of the county sending more than 74,000 mail-in ballots. He also said auditors found approximately 18,000 people voted but were removed from voter rolls “soon after the election, 11,326 people who were not on the voter rolls on Nov. 7, 2020, but appeared on the rolls on Dec. 4, 2020, and 3,981 people who voted after registering after Oct. 15, 2020.”
Ben Cotton, CEO of CyFIR, a subcontractor working on the audit, said the analysis of the election management system and network uncovered “severe cybersecurity problems,” including that antivirus programs weren’t up to date.
The hearing came after Arizona Senate President Karen Fann, whose Republican caucus authorized the audit late last year, said the auditors’ ballot count produced a different number from the county’s count.
Logan said the discrepancies with mail-in ballot records should trigger a canvassing proposal that was put on hold under pressure from the Department of Justice.
(Excerpt) Read more at theepochtimes.com ...
Thanks for that explanation. But it seems like a critical flaw for any security software to have such an easily exploited limit. Let the log file increase to the capacity of the drive because the only reason for it to grow to that ridiculous size is when someone is trying to obfuscate the log.
Great ideas, but there is no “ballot referendum” in VT. Not that it would matter in “the Peoples Republic”.
Spelunking logs would be something entirely different than to splunk a log, which I do most every morning.
Right. Like I said, often the size is configurable. In many systems I work with, when we set them up, we create a separate drive to be used for log files only, and will make it 200 or even 500MB. And then you have to configure logging behavior. I work with some sharp guys, and have learned a lot about this aspect.
But one thing that sucks is that there are many systems, when they cannot write to a file, the system either stops working, or begins working erratically.
The first few times I ran into this, I was flummoxed, but as I gained experience, it became one of the first things I looked at. Only took a second to peek...
Of course, there may have been a valid reason someone ran a script all those times.
What could a valid reason be to run it 37,000 times on one day?
More than the President, it’ll be interesting to see how this plays with regards to the Senate races. If they can toss Kelly, Warnock and Ossoff on the street CornPop and Harris, at least, should be dead in the water.
It would not surprise me to find out that Biden got less than 20 percent of the legal vote.
LOL, no reason I could think of, and I gave it some thought.
Occam’s Razor, my FRiend...:)
That’s what I thought. Just curious if there was something I was missing, thx
Bkmk splunk
Thanks for posting that. Most of what you said i know and note it.. But my GF and a lot of people don’t understand the details. I forget that not everyone knows the implications of the logs filling up with what looks like a dummy script.
https://patriots.win/p/12jJimWiW0/arizona-state-senate-hearing-jul/c/
In a race decided by 10,457 votes...
• 74,243 mail-in ballots found with NO clear record of them ever being sent.
• 3,981 voted despite having registered AFTER October 15 deadline
• 11,326 voted who were NOT on rolls on Nov 7, 2020 but WERE on Dec 4
• 18,000 voted but then were removed from rolls AFTER election
• Maricopa did not put serial numbers on original and duplicated ballots and so cannot ensure ballots were accurately duplicated or how many times they were duplicated.
• The number of votes certified did not match the number of ballots sent to the audit.
• Digital forensic expert Ben Cotton revealed the Maricopa County election system was BREACHED during the course of the 2020 election.
• Anti-virus updates had not been downloaded since August, 2019. Typically done once a week. This allowed access to server & systems.
• On March 11 there were over 37,000 queries for a blank password on one Maricopa system that only had 8 accounts. The script used was for the EMS (Election Management System) Administrator account. Who was using the EMS admin account? The audit team has not been able to determine that. Maricopa County refuses to hand over the routers which have been subpoenaed.
• All access logs were wiped in March 2021. Access logs provide a record of which accounts accessed files on the system and when.
• Ballot calibration was off by an average of 1000% leading to bleed-through, which can cause over-votes and inaccurate vote attribution (the ascribing of a vote to a ballot). The on-demand ballots (those printed at the voting centers on Election Day) have the worst calibration issues. More than 168K ballots were affected.
• The County has stated they use thick VoteSecure paper, meant to limit bleed-through in the event of mis-calibration. The audit team (Cyber Ninjas) has found a large number of ballots printed on very thin paper stock.
AZ State Senator Wendy Rogers: “I have heard enough. With the mailing of tens of thousands of unrequested ballots; the over 10,000 people who registered and voted after November 3rd; with Maricopa County’s failure to turn over the 40% machines; with Dominion’s refusal still to turn over passwords, with the tens of thousands of unauthorized queries demonstrating how insecure the election was,I call for the Biden electors to be recalled to Arizona and a new election conducted. Arizona’s electors must not be awarded fraudulently. We need to get this right
1) A company should step forward with an utterly transparent voting process that can be quickly and reliably audited. Results in 24 hours. Exactly what happened. That company ought to be able to do hefty business in all 50 states. Which brings me to point #2.
>>> i think XEROX could do it with all kinds of paper document controls. Printing and processing mailin ballots, scanning and crunching, etc. there are others. When i put out a RFP for document processing i got a lot of responses. When the details involved banking back and forth they all begged off. I think FISERV is another company . They can hadle the document processing. The mail in ballot stuff is a lot and my current recommendation to all my elected officials that i email all the time. “ as nice as these people are. They should never ever be anywhere near something that has an electrical plug in it.”
Splunking is a term and method I learned in 2004.
BTW, I use Notepad++...brilliantly good. Free, and opens up the largest files nearly instantly.>>> And it has colors if you code java in it.
why those router logs are needed.>>>
Another great thing in all of this is that these guys are smarter than anyone working or near government employment. fun to watch.
Its more than that.
You can splunk information from one application into another application.
So is there a process to de-certify electoral college votes in states?That, in a way was VP Mike Pence's job.
All of the Pence apologists would tell you that Pence's constitutional duty was to rubber stamp the certification. One of them even said that in so many ways (you know who you are)
Let's see? Arizona? Arizona?...OH That's right, now I remember. Arizona is the state Fox called for Biden before the pols closed.
People were still waiting in line to vote. The Tucker, Ryan, Fox cabal couldn't take any chances that Trump might win, they had to act fast.
BTTT
There’s no good reason to have one single 20mb log file, unless your plan is to be able to wipe it easily with a script to cover your tracks.
A Cisco router default log:
“The typical default size of a router’s logging buffer is 4,096 bytes (although some high-end routers will default to a higher value). A buffer of this size can hold approximately 50 log messages before overwriting occurs. Fifty messages, although better than no logging, is relatively small, and most engineers will want increase their buffer size to store more messages”
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.