[/url]ICT ACCESS/AUDIT:15(a) software application installed from Sotik in Bomet,multiple uploading of the same Form 34B, modification & deletions pic.twitter.com/a93gevfQJA
— Apollo Mboya, HSC (@MboyaApollo) August 29, 2017
[/url]ICT ACCESS/AUDIT:16-Misuse of accounts,deletion of commands on 8th August & 17th August 2017 pic.twitter.com/KYtAzaIHkk
— Apollo Mboya, HSC (@MboyaApollo) August 29, 2017
The court erred in not accepting help (amicus curi) of an IT specialist. They should have accepted the request by the Kenya ICT Association Network. One wonders why the court declined to admit KICTANET as a friend of the court. Would have helped a great deal in clarifying some of these things. I dare say some of the judges may have been sold to the yarn of the firewall being a really "impenetrable wall" in its literal sense.....
The court erred in not accepting help (amicus curi) of an IT specialist. They should have accepted the request by the Kenya ICT Association Network. One wonders why the court declined to admit KICTANET as a friend of the court. Would have helped a great deal in clarifying some of these things. I dare say some of the judges may have been sold to the yarn of the firewall being a really "impenetrable wall" in its literal sense.....
Just read the NASA it audit and there is nothing there to suggest any foul play.Certainly nothing to be used in presidential petitions.IEBC need to commended for rolling out systems that worked in some of the toughest places.All you see are some staff struggling to upload forms.
What software did he install.Maybe ms word.This internal iebc systems.Those that struggled most likely got help from iebc staff to upload staff.No where in statures or laws define how iebc should structure it's IT systems.The point that NASA need to proof is whether systems was hacked or not.it wasn't. The systems has not be compromised.Raising suspicion is not enough in court of law.
Or guest logins. Imagine 41K users. All this conjecture instead of just tabling photos of materially different forms. The burden of proof is on the petitioner not IEBC.What software did he install.Maybe ms word.This internal iebc systems.Those that struggled most likely got help from iebc staff to upload staff.No where in statures or laws define how iebc should structure it's IT systems.The point that NASA need to proof is whether systems was hacked or not.it wasn't. The systems has not be compromised.Raising suspicion is not enough in court of law.
Or guest logins. Imagine 41K users. All this conjecture instead of just tabling photos of materially different forms. The burden of proof is on the petitioner not IEBC.What software did he install.Maybe ms word.This internal iebc systems.Those that struggled most likely got help from iebc staff to upload staff.No where in statures or laws define how iebc should structure it's IT systems.The point that NASA need to proof is whether systems was hacked or not.it wasn't. The systems has not be compromised.Raising suspicion is not enough in court of law.
40,000 is indeed a lot. I would imagine the main application would have one login. Guest logins should raise alarms about the level of security. KPMG did mention horrendous security. But apparently they were given the old system to audit.
What software did he install.Maybe ms word.This internal iebc systems.Those that struggled most likely got help from iebc staff to upload staff.No where in statures or laws define how iebc should structure it's IT systems.The point that NASA need to proof is whether systems was hacked or not.it wasn't. The systems has not be compromised.Raising suspicion is not enough in court of law.
Or guest logins. Imagine 41K users. All this conjecture instead of just tabling photos of materially different forms. The burden of proof is on the petitioner not IEBC.What software did he install.Maybe ms word.This internal iebc systems.Those that struggled most likely got help from iebc staff to upload staff.No where in statures or laws define how iebc should structure it's IT systems.The point that NASA need to proof is whether systems was hacked or not.it wasn't. The systems has not be compromised.Raising suspicion is not enough in court of law.
40,000 is indeed a lot. I would imagine the main application would have one login. Guest logins should raise alarms about the level of security. KPMG did mention horrendous security. But apparently they were given the old system to audit.
41k users is indeed a large number, but we need to remember that the actual "work" done by these users was quite narrow if I have understood it correctly. Log in>upload 34A>type number of votes by candidate>click send>log out. I do not think these were resource intensive to a point of the system breaking.
Or guest logins. Imagine 41K users. All this conjecture instead of just tabling photos of materially different forms. The burden of proof is on the petitioner not IEBC.What software did he install.Maybe ms word.This internal iebc systems.Those that struggled most likely got help from iebc staff to upload staff.No where in statures or laws define how iebc should structure it's IT systems.The point that NASA need to proof is whether systems was hacked or not.it wasn't. The systems has not be compromised.Raising suspicion is not enough in court of law.
40,000 is indeed a lot. I would imagine the main application would have one login. Guest logins should raise alarms about the level of security. KPMG did mention horrendous security. But apparently they were given the old system to audit.
41k users is indeed a large number, but we need to remember that the actual "work" done by these users was quite narrow if I have understood it correctly. Log in>upload 34A>type number of votes by candidate>click send>log out. I do not think these were resource intensive to a point of the system breaking.
You right there was nothing resource intensive about this system. To be fair, I was just suggesting a possible and typical configuration of such apps.
One real login to the main system that belongs to the main application. This application in turn provides access to end users through virtual logins.
I have actually seen a statement to the effect that on Election Day, there was nothing that came into the system from polling stations, or something to that effect - I'll try share it when I can. It's what partly makes me lean towards a system failure.
I have actually seen a statement to the effect that on Election Day, there was nothing that came into the system from polling stations, or something to that effect - I'll try share it when I can. It's what partly makes me lean towards a system failure.
What software did he install.Maybe ms word.This internal iebc systems.Those that struggled most likely got help from iebc staff to upload staff.No where in statures or laws define how iebc should structure it's IT systems.The point that NASA need to proof is whether systems was hacked or not.it wasn't. The systems has not be compromised.Raising suspicion is not enough in court of law.
Who knows. I think it would be ignorant to expect that the "hacker" would label his worm as "rigging algorithm" for the benefit of any future auditors. Or even better still not claim that they were installing something that they were not supposed to. The starting point is that whoever it was, was up to some sort of mischief or criminal intent.
Nothing innocent here.
Or guest logins. Imagine 41K users. All this conjecture instead of just tabling photos of materially different forms. The burden of proof is on the petitioner not IEBC.What software did he install.Maybe ms word.This internal iebc systems.Those that struggled most likely got help from iebc staff to upload staff.No where in statures or laws define how iebc should structure it's IT systems.The point that NASA need to proof is whether systems was hacked or not.it wasn't. The systems has not be compromised.Raising suspicion is not enough in court of law.
40,000 is indeed a lot. I would imagine the main application would have one login. Guest logins should raise alarms about the level of security. KPMG did mention horrendous security. But apparently they were given the old system to audit.
41k users is indeed a large number, but we need to remember that the actual "work" done by these users was quite narrow if I have understood it correctly. Log in>upload 34A>type number of votes by candidate>click send>log out. I do not think these were resource intensive to a point of the system breaking.
You right there was nothing resource intensive about this system. To be fair, I was just suggesting a possible and typical configuration of such apps.
One real login to the main system that belongs to the main application. This application in turn provides access to end users through virtual logins.
I have actually seen a statement to the effect that on Election Day, there was nothing that came into the system from polling stations, or something to that effect - I'll try share it when I can. It's what partly makes me lean towards a system failure.
The cynical me, tends to lean towards "system switch off" to allow for the rigging server to take over processes and deliver the predetermined "winner". I suspect it would have been easier to render parts of the infrastructure unusable than to have in place a blanket instruction to the polling centre IEBC staff to not send the data back.
Just read the NASA it audit and there is nothing there to suggest any foul play.Certainly nothing to be used in presidential petitions.IEBC need to commended for rolling out systems that worked in some of the toughest places.All you see are some staff struggling to upload forms.(http://omollosview.com/wp-content/uploads/2017/08/sotik.jpg)