Kohezion

10/15/2026

How your account is configured is a question about today. Who signed in last Tuesday is a question about a moment that has already passed.

Our new piece closes the series with three things that tell you what your own sign-in records can answer.

Read it: https://www.kohezion.com/blog/sign-in-records

10/13/2026

Passkey sign-in is available on Kohezion Enterprise accounts. Use it alongside the password, or in place of it.

Our new guide covers both options, what happens for staff who cannot carry a phone, and the one place passkeys do not fit.

Read it: https://www.kohezion.com/blog/passkey-sign-in

10/08/2026

How long should a device stay trusted after somebody has already proved who they were?

Ask any vendor for the maximum, not just the default. The default is where the setting starts. The maximum is how far it can go once somebody else is deciding.

Our new piece covers the three things that should decide yours.

Read it: https://www.kohezion.com/blog/trusted-devices

10/06/2026

Deciding to require multi-factor authentication is the easy half. Getting everyone enrolled without a difficult week takes more thought.

Our new guide covers grace periods, the short hardship route, and why staff and partners should move separately.

Read it: https://www.kohezion.com/blog/mandatory-mfa-enrollment

10/05/2026

October is Cybersecurity Awareness Month, which mostly means posters about passwords.

Those posters are worth having. But the question that turns up in an audit is a different one: who could reach a particular record, and can you show it?

One of those depends on people remembering. The other depends on how the system was built.

10/01/2026

When three people use one login, every record that account approved becomes unattributable. Including the ones handled perfectly.

Our new piece covers why sharing persists, and the one thing we have seen actually end it.

Read it: https://www.kohezion.com/blog/shared-logins

09/29/2026

App, emailed code, or passkey? The useful question is not which is strongest. It is which one your people can use every day without working around it.

Our new guide compares all three on what each one asks of the person signing in.

Read it: https://www.kohezion.com/blog/two-factor-authentication-options

09/24/2026

Access starts tight. Then an exception is granted to unblock the work, and nobody revisits it. A year later the list describes nobody's intention.

Our new piece covers how to review it in a morning, and who should be doing the checking.

Read it: https://www.kohezion.com/blog/user-access-review

A user access review catches the permissions that built up one exception at a time. Most organizations find theirs during an audit.

09/22/2026

Knowing who can sign in is the easy half. Deciding what each person reaches once they are in is the half that carries the obligation.

Our new guide breaks it into six decisions, from whole areas of work down to a single field.

Read it: https://www.kohezion.com/blog/user-permissions

09/17/2026

Result 1, Result 2, Result 3.

If your fields have numbers in them, your work grew a second layer and the structure never caught up.

Our new piece covers how to spot that moment, whether to fix it now or later, and the one question worth asking before adding any new field.

Read it: https://www.kohezion.com/blog/one-to-many-relationships