Account access and audit-record protections in Military OS

Authenticator MFA for password accounts

The sign-in configuration requires an authenticator app for every password account, including members and administrators. After entering a password, the person uses a temporary code from their authenticator app. This multi-factor authentication (MFA) requirement is part of the deployment configuration. Live enrollment and recovery still need verification at each client launch.

Email supports password recovery. Returning password sign-ins still require the authenticator step. Separate operator and support accounts need their own access checks.

Session revocation and account blocking

App sessions expire after a maximum of eight hours. Authenticated requests check that the session is still valid and load the person's current access, roles and membership information.

An approved operator procedure can revoke all current app sessions for a person or block the account from creating new app sessions. Blocking is separate from membership and payment history. Removing a staff role also takes effect when the application next reads the person's access information.

Restricted database duties

The web application can record and read administrative activity. Its database access cannot rewrite or delete those audit records, change the database structure, or run scheduled audit maintenance.

A separate maintenance account can run only the fixed audit-retention procedure. It cannot choose different retention dates or directly read member records and change audit evidence.

Keeping award-linked evidence

The standard retention window is 18 months. Records linked to award history are kept beyond that window. Other records stored in the same monthly group may also be retained.

Historic activity retains the original recorded actor when a person record is merged or deleted. The activity screen can show the earlier person's stored name where available, while the restricted web login cannot rewrite those audit details.

Security verification

Automated tests cover selected account-access rules, database permissions and audit-retention behavior. These checks run locally. Verification in a live hosted environment remains outstanding.

Before each customer installation goes live, we must verify sign-in and recovery, account blocking and session revocation, encrypted connections, scheduled maintenance and monitoring.

Screenshots show the product version available when this post was published.