IT security consultant.

Joined September 2010
.@LeontineLoeber taking disinformation in elections and the Digital Service Act, by the EU. Risks and shortcomings of the legislation. #EVoteID2024
1
3
223
.@davidduenascid talking about trust vs distrust as separate metrics. Here reviewing the case of machine voting in the Netherlands... #EVoteID2024
53
.@LeontineLoeber introducing the recently released special issue of @JeDEM_journal with papers from last year #EVoteID2024
1
1
2
520
🗳️Des d'avui i fins divendres, els principals experts en votació electrònica es reuneixen a #Tarragona, en un congrés internacional del qual la #URV n'és un dels organitzadors i on es debat sobre ciberseguretat, criptografia i gestió electoral. 👉diaridigital.urv.cat/tarrago…
2
7
473
Just out: new issue of JeDEM, including papers from the 2023 E-Vote-ID Conference. The issue explores issues such as the transparency of internet voting, trust and distrust in election technologies and their administration by electoral management bodies. jedem.org/index.php/jedem/is…
3
6
245
The E-Vote-ID 2023 special issue of JeDEM is now out, in time for #EVoteID2024 jedem.org/index.php/jedem/is…
30
.@aleksessex: "vendor name redacted] claims that their system encrypts the ballots, because they use transport level encryption". *audience bursts out with laughter* Thanks Aleks for underlining the difference between marketing claims and facts. #EVoteID2024
2
4
379
One of the exceptional thingd about this conference is that the reviewed papers are already available, in open format, made possible by @KASTEL_SRL. So even if you are not here, we invite you to read the latest research on voting and technologies #EvoteID2024.
1
2
3
287
In Tarragona, for #EVoteID! Looking forward to discuss the papers, have chats, and enjoy tapas...
1
59
The @EVoteID proceedings for #EvoteID2024 conference, published with @SpringerNature, are already out and available in open access (thanks @KASTEL_SRL for the generous contribution). Read and enjoy: link.springer.com/book/10.10…
6
10
337
Please share this far and wide. As far and wide as you can. NIST Password Guidelines for 2024 are in the process of being updated. This is a HUGE pet-peeve of mine (when vendors in particular are still operating like its 2017 and keep changing passwords every 60 days, STOP DOING THIS, it's outdated and has been shown to put you MORE at risk than less -- NIST explains why it does in this document, meticulously outlining user behavior**) so I'm sharing this in the hopes all of you will pass it along to your bosses. The Special Publication series governing passwords is SP 800-63 "Digital Identity Guidelines". The 2024 version is 800-63-4. Here: pages.nist.gov/800-63-4/ The companion docs are also on that link. They are 800-63A, 800-63B and 800-63C. These are different documents for different scenarios in play at your org. The previous update was in2020. The changes in the 2020 version from the 2017 version were numerous but one of them was that the password verification method should NO LONGER require passwords be changed at specific intervals (i.e. every 60 days) but in the following circumstances instead: 1. After a breach/compromise 2. User request 2024 repeats this and adds a bunch more guidlines but here is a screenshot of page 13 of the new 800-63-4 (note the # 4 after it) which outlines how your systems should now and moving forward, be handling passwords. This goes for Active Directory, too. All your systems which have passwords should align with these guidelines provided there isn't another standard or framework you must adhere to which overrules this. Most frameworks, however, have moved away from arbitrary password resets and complexity rules. **We cybersec researchers and hackers use wordlists from breaches in a variety of different ways. Hackers use them in tooling to crack passwords whereas researchers use breach dumps to see the kinds of passwords users are creating and the psychology behind them. Using complexity rules gets you the user psychology of: Password1 Password2 and so on Use phrasing instead and allow for spaces, which is important. Humans type phrases with spaces. They also mention phish-resistant methods and most vendors are on-board with MS going to be turning off all Legacy Auth next month, across all free accounts and tenancies. I'm so excited for the new changes! Ok I'm off my soapbox. Share the love! Thank you!
183
1,761
202
5,414
646,739
It is the last day of the early-bird discount when registering for #EvoteID2024. So make sure you have your spot for this great conference! @pereiraucl, @nicolejgoodman, @LeoFel_Official @LeontineLoeber, @philipbstark, @CESchuermann! Register at congressos.urv.cat/e-vote-id…
4
7
879
To recap: keynoyes by Lexi Merrick Boiro, Feng Hao and Michelle Brown. Panels on Technical and Governance issues. Case studies, demos and a poster session. Many interesting people, the lastest research and all that in beautiful Tarragona. Don't miss out!
4
6
357
This year's #EvoteID2024 is approaching! Find the list of accepted papers here and don't miss the chance to join the conference! Early bird registration finishes on September 15! Register here --> congressos.urv.cat/e-vote-id…
1
7
1
8
810
Hey all! If you, or anyone you know, might be interested in the use of technology in voting processes or have practical experiences to share, there's still almost one week left to submit to e-vote-id on the practitioners' track or for the PhD colloquium! e-vote-id2024.org
3
49
Are you an EMB that has experience with the use of technology in elections? Do you have an interesting case study that you want to present at #EvoteID2024? The deadline for track 3 is July 10th, so there is still time to submit it!
1
6
4
868
Thomas Hofer retweeted
Hey @Redisinc - suppose I want to disclose a security vulnerability in your stack but don’t want to file an open issue on GitHub - what should I do?
1
2
3
4
3,213
If your interests lie in Security, Usability, and Technical Issues of electronic voting (Track 1, chaired by @JBudurushi and @MichelleBlom8) or in Governance Issues of the electronic voting (Track 2, chaired by @adriarope and @JKrivonosova), don't miss the date.
1
3
4
250
A customer once insisted his account couldn't be compromised due to his use of 2FA I explained that 2FA provides no protection if a threat actor obtains his access token It's alarming how many are unaware of the inherent weaknesses in token-based access
27
58
1
408
59,008