Secure Ballot Software: What Makes an Online Ballot Secure?

Thursday, 24 September 2026, 10:43 am

Why Electronic Voting Audit Trails Are Essential for Trust and Compliance
BlogElections

What is secure ballot software?

Secure ballot software is designed specifically to manage formal voting processes while protecting the people, information and decisions involved.

Depending on the type of ballot, that can include controls for:

Voter eligibility.
Authentication.
One-person-one-vote requirements.
Voting entitlements.
Ballot secrecy.
Proxy voting.
Administrator permissions.
Encryption.
Audit trails.
Result calculation.
Election reporting.

The exact requirements will depend on the organisation and the rules applying to the vote.

A board election, for example, may have very different requirements from a shareholder resolution or a workplace ballot.

That distinction matters when choosing a provider. The question is not simply whether the software is “secure”. It is whether the security controls are appropriate for your particular voting process.

Why online ballot security matters

A voting system can produce a technically correct result and still leave an organisation with difficult questions to answer.

Consider a member election where someone later says:

“I was eligible but could not access my ballot.”
“Someone appears to have voted using my credentials.”
“How do we know a vote wasn’t submitted twice?”
“Who changed the election settings?”
“Can you prove when voting closed?”
“Was my vote actually included in the count?”
“Can you prove that nobody could see how I voted?”

These are governance questions as much as technical questions.

A secure ballot should give administrators enough evidence to investigate legitimate concerns without creating unnecessary access to confidential voting information.

The Australian Government’s cyber security guidance takes a similar layered approach to information security. Controls such as multi-factor authentication, access restrictions, event logging and protection of logs work together rather than relying on one security measure.

1. Voter authentication: making sure the right people can vote

The first security question is straightforward: Is this person entitled to vote?

A formal ballot should have a reliable way of establishing voter eligibility before someone is allowed to submit a ballot.

That might involve unique voting credentials, secure links, PINs, member identifiers or another authentication method suited to the risk and structure of the election.

The important thing is that authentication should be tied to the voting rules.

For example, if every eligible member is entitled to one vote, the system should be able to prevent the same voting entitlement from being used more than once.

Australian Cyber Security Centre guidance identifies multi-factor authentication as an important control for protecting online services and sensitive information. Its current guidance also addresses MFA for third-party online services and privileged users.

That does not mean every voter must necessarily use the same authentication method.

A better question for an organisation is: What level of authentication is appropriate for this particular ballot?

Questions to ask your voting provider

When assessing a provider, ask:

How is the voter roll established?
How is eligibility verified?
Does each voter receive a unique voting credential?
Can a credential be reused?
What happens when a voter loses access?
How are administrator accounts protected?
Are privileged accounts protected with stronger authentication?
Are authentication events logged?

2. Encryption: protecting information as it moves and is stored

Encryption is another fundamental part of online voting security.

There are two areas to consider.

Encryption in transit

When a voter accesses a ballot and submits their vote, information travels between their device and the voting platform.

Encryption helps protect that communication from unauthorised access or manipulation.

The Australian Cyber Security Centre’s Information Security Manual includes controls concerning the protection of information and event logs in transit using approved cryptography.

For an online ballot, that protection can apply to communications involved in:

Accessing the voting platform.
Authentication.
Submitting a ballot.
Communicating with the voting application.
Administering an election.

Encryption at rest

Voting information may also be stored in databases, backups and other systems.

Encryption at rest provides another layer of protection for stored information.

When assessing a provider, therefore, don’t stop at:

“Is the platform encrypted?”

Ask:

“What information is encrypted, both in transit and at rest, and how is that protection managed?”

That is a much more useful conversation.

3. Audit trails: knowing what happened

A secure ballot should not leave the organisation with only a final number.

The organisation should also have appropriate evidence of how the voting process operated.

An audit trail is a chronological record of significant events during the election.

Depending on the voting system, that could include:

Election creation.
Ballot publication.
Voter authentication.
Ballot access.
Vote submission.
Administrator actions.
Changes to election settings.
Election closure.
Result generation.
Report creation.

The Australian Cyber Security Centre’s current guidance places significant emphasis on event logging and protecting logs from unauthorised modification or deletion.

For an organisation running a formal election, this creates an important distinction: A result tells you what happened. An audit trail helps demonstrate how it happened.

That becomes particularly useful when a result is questioned.

What should a voting audit trail record?

A useful audit trail should provide enough information to reconstruct the important stages of an election.

For example, it may show:

Voting opened at the scheduled time.
Eligible voters were authenticated.
Ballots were submitted.
The election closed.
The result was generated.
Administrative activity was recorded.

The exact information will depend on the election.

The audit trail should also be protected against inappropriate alteration. Australian Government guidance specifically identifies protection of event logs from unauthorised modification and deletion as a security control.

4. Vote integrity: protecting the vote itself

Authentication tells you who is entitled to vote.

Encryption helps protect information.

Audit trails help show what happened.

But there is another question: Can the vote itself be trusted?

Vote integrity means protecting the ballot from unauthorised alteration, duplication, loss or manipulation.

For a simple one-person-one-vote election, a secure system should be able to establish that:

The voter was eligible.
The voter was authenticated.
Their voting entitlement was used appropriately.
The ballot was successfully submitted.
The vote was included in the count.
The election records were protected from unauthorised alteration.

Vero’s recent guidance on secure online voting similarly identifies duplicate-vote prevention and audit logging as important controls within an online voting process.

The important point is that vote integrity is not just about the counting algorithm. It starts before the voter even reaches the ballot.

Authentication and anonymity are not the same thing

This is one of the most important concepts to understand when evaluating secure ballot software.

A secret ballot needs to answer two different questions:

Authentication: Is this person entitled to vote?

Ballot secrecy: Can anyone determine how this person voted?

Those requirements can coexist.

A properly designed secret ballot can verify that an eligible member participated without exposing that member’s individual voting choice.

For example, the system may need to establish:

Member A was eligible.
Member A received access to the ballot.
Member A submitted a vote.
Member A’s voting entitlement cannot be used again.

But where the ballot is secret, it should not expose:

Member A voted for Candidate 1.

That separation between identity and vote data is central to anonymous online voting. Vero’s published guidance describes the same principle: voter participation can be recorded while the ballot choices are kept separate.

This is also why simply hiding voting results from administrators is not the same as providing a secret ballot.

The underlying system needs to be designed appropriately.

Administrator security matters too

Organisations often spend considerable time thinking about voter security and much less time considering administrator access.

That can be a mistake.

Someone administering an election may have access to:

Voter information.
Election settings.
Voting dates.
Permissions.
Reports.
Results.

Administrator accounts therefore need appropriate access controls.

The Australian Cyber Security Centre’s current guidance includes MFA for privileged users and recommends centrally logging authentication events.

A voting provider should be able to explain:

Who can create an election.
Who can change its settings.
Who can access voter information.
Who can view results.
Who can close a ballot.
How administrator actions are recorded.
How permissions are restricted.

Not every administrator needs access to everything.

That is where role-based access becomes useful.

What does privacy have to do with ballot security?

Online ballots can involve personal information such as names, contact details, membership records, voting credentials and participation information.

For organisations covered by the Australian Privacy Principles, APP 11 requires reasonable steps to protect personal information from misuse, interference and loss, as well as unauthorised access, modification or disclosure. The OAIC’s current guidance was updated on 3 October 2025 and explains that reasonable measures include both technical and organisational controls.

The OAIC also recommends considering security across the information lifecycle, from collection through to destruction or de-identification when information is no longer needed, subject to applicable retention requirements.

For a voting organisation, that means asking more than:

“Is the ballot secure?”

It is worth asking:

What personal information does the voting provider actually need?
Where is that information stored?
Who can access it?
How long is it retained?
What happens to it after the election?
How does the provider manage third-party services?
What happens if there is a data breach?

The OAIC specifically identifies third-party providers, cloud computing, ICT security, access security, data breaches and information lifecycle management as areas to consider under APP 11.

What about ISO 27001 and SOC 2?

Security certifications and independent assurance can be useful when comparing voting providers.

ISO/IEC 27001:2022 specifies requirements for an Information Security Management System (ISMS). ISO describes the standard as a framework for managing information security risks through a structured approach covering confidentiality, integrity and availability.

SOC 2 Type II is another form of independent assurance that organisations may encounter when assessing technology providers.

These forms of assurance are useful evidence, but they should not be treated as proof that every aspect of a particular voting process is suitable.

There are really two separate questions:

How does the provider manage information security?

and

How does the voting platform protect this particular election?

A provider should be able to answer both.

Vero Voting states that it is ISO/IEC 27001:2022 certified and SOC 2 Type II audited.

Those credentials sit alongside the election-specific controls rather than replacing them.

Common mistakes when choosing secure voting software

Mistake 1: Assuming a survey tool is an election platform

A survey application can collect responses.

That does not automatically mean it can manage a formal election.

An election may require voter authentication, eligibility controls, ballot secrecy, one-person-one-vote rules, proxy management, weighted voting, audit records and formal result reporting.

The organisation needs to match the software to the voting process.

Mistake 2: Focusing only on encryption

Encryption matters, but it is one layer of security.

A system could have strong encryption and still have poor administrator controls or inadequate ballot-secrecy arrangements.

Look at the complete security architecture.

Mistake 3: Treating a login as authentication

Having a username and password does not, by itself, answer every voter-authentication question.

Ask how credentials are issued, protected, recovered and invalidated.

Mistake 4: Forgetting about the audit trail

If a provider can give you the result but cannot clearly explain what evidence exists behind that result, ask more questions.

A formal election should leave an appropriate record of the process.

Mistake 5: Confusing anonymity with hiding the result

Keeping results confidential until an election closes is not the same thing as protecting ballot secrecy.

For a secret ballot, the underlying system needs to protect the connection between voter identity and voting choice.

Mistake 6: Assuming certification eliminates cyber risk

ISO/IEC 27001 certification and other independent assurance can provide valuable evidence of security governance.

They do not mean a system can never be compromised.

Vero’s own recent discussion of independent security audits makes the same point: security assurance provides evidence that controls have been assessed, but security remains an ongoing process involving monitoring, testing, vulnerability management and incident response.

A practical secure ballot software checklist

Security area Questions to ask
Voter authentication How does the system confirm that someone is entitled to vote?
Access control How are voter and administrator accounts protected?
MFA Is MFA available for administrators and other privileged users?
Encryption Is data protected in transit and at rest?
Ballot secrecy Can voter identity be separated from ballot choices?
Vote integrity How does the platform prevent duplicate or unauthorised voting?
Audit trail Which election and administrative events are recorded?
Audit protection Can historical records be altered or deleted?
Administrator access Can permissions be restricted by role?
Personal information What information is collected and how is it protected?
Data retention What happens to voter information after the ballot?
Independent assurance Has the provider’s security environment been independently assessed?
Incident response What happens if a security incident occurs?
Reporting What evidence is available after voting closes?

A provider that can answer these questions clearly is giving you something much more useful than a generic “enterprise-grade security” statement.

Where Vero Voting can assist

Vero Voting works with Australian organisations running formal voting processes including AGMs, member elections, board elections, enterprise agreement votes and other governance ballots.

Security is built into the wider voting process rather than treated as a separate feature.

Vero’s published information describes secure voter authentication, audit trails, ballot-secrecy controls and security assurance measures. Its AGM service page states that Vero is ISO/IEC 27001:2022 certified and SOC 2 Type II audited.

That combination matters because a secure ballot is not just about protecting a database.

The organisation needs confidence in the whole process — from voter access through to the final result.

For organisations that need an independent record of voting activity, Vero also provides audit trails designed to document significant election events while protecting ballot secrecy.

If you’re reviewing an existing voting process or planning an upcoming ballot, contact Vero Voting or request a demonstration to see how the security and audit process works in practice.

Key Takeaways

A secure online ballot needs more than a secure website.

The main areas to examine are:

Authentication — only eligible voters should be able to access and use their voting entitlement.
Encryption — information should be appropriately protected while travelling between systems and when stored.
Audit trails — significant election events should be recorded and protected from unauthorised alteration.
Vote integrity — the system should protect votes from unauthorised changes, duplication or loss.
Ballot secrecy — where a secret ballot is required, voter identity and voting choices need to be appropriately separated.
Administrator security — privileged access should be controlled and monitored.
Privacy — personal information should be protected throughout its lifecycle.
Independent assurance — recognised standards and independent assessments can provide additional evidence about a provider’s security practices.

The best security questions are not simply technical ones.

Ask what happens when a real voter needs help, an administrator changes a setting, a ballot is challenged or someone wants evidence of how the result was produced.

That is where secure ballot software earns its place in a formal governance process.

Sources

Australian Government and regulatory authorities

Australian Cyber Security Centre — Implementing multi-factor authentication
Australian Cyber Security Centre — MFA guidance
Australian Cyber Security Centre — Essential Eight maturity model
Australian Cyber Security Centre — Essential Eight maturity model
Australian Cyber Security Centre — Guidelines for system access
Australian Cyber Security Centre — Guidelines for system access
Australian Cyber Security Centre — Guidelines for security assurance
Australian Cyber Security Centre — Guidelines for security assurance
Office of the Australian Information Commissioner — APP 11
OAIC — Security of personal information
ISO — ISO/IEC 27001:2022
ISO — ISO/IEC 27001:2022

Frequently Asked Questions

What is secure ballot software?

Secure ballot software is designed to run formal elections and ballots while protecting voter access, personal information, ballot secrecy and vote integrity. It can include authentication, encryption, access controls, audit trails and secure result reporting.

How is an online ballot kept secure?

Online ballot security relies on multiple controls working together. These can include voter authentication, encryption, administrator access controls, duplicate-vote prevention, protected audit logs and appropriate separation of voter identity from ballot choices.

Can an online ballot be anonymous and still be audited?

Yes. A properly designed secret ballot can record that an eligible voter participated while keeping their voting choice separate from their identity. This allows the process to be audited without unnecessarily exposing individual votes.

Is encryption enough to make online voting secure?

No. Encryption is one part of a broader security framework. A secure voting system also needs appropriate authentication, access controls, auditability, vote-integrity measures and ballot-secrecy arrangements.

What should I ask an online voting provider about security?

Ask how the provider verifies voter eligibility, protects administrator accounts, encrypts information, prevents duplicate voting, protects audit logs, maintains ballot secrecy, handles personal information and responds to security incidents. It is also worth asking about independent security certification or assurance.

Need support with your next Elections?

Contact Us

Subscribe to our blog

Stay up to date on the latest topics for voting solutions

[stc-subscribe]



    Subscribe

    If you want to personalise your subscription, click here