Repository navigation
Releases
ArgueSecure 2.8.1
ArgueSecure 2.8.1
One registration switch for email and single sign-on, clearer report settings and Strength tab, and a round of fixes to the administration pages.
Sign-in and security
-
One registration switch. Allow new registrations now covers both ways in. With it on, a first single sign-on login creates an ordinary, non-administrator account when the provider marks the email as verified and the address is on the single sign-on domain list (empty means every domain) and, if you set one, on the email-registration list. Nobody is sent mail for this: the provider has already proved the address. With it off, single sign-on links to an existing account with the same verified email but creates none. The switch can be turned on with email set up or single sign-on set up.
-
Google sign-in has now been tested against a live Google account. Only Keycloak and Google have been tested; other providers, Microsoft Entra ID included, are expected to work but are unverified.
-
Dependency security update. Laravel is updated to 12.72.0, with its minor dependencies, to fix a published advisory in its concurrency tasks.
Editing
- Strength tab. A defence opened from an attack shows that attack's strength first, in a highlighted block; the defence's other attacks sit in a collapsed list below. When there is no known parent (a direct link, or a single attack) nothing is split.
- Suggest buttons look different from Add buttons: a sparkles icon in the accent colour.
- The assessment list no longer shows a Settings icon on each row. Settings open from the action bar inside an assessment.
Reports
- Report settings are four panels: Sections, Appendices (references, methodology, warnings), Details (show comments, show assignees) and the existing Defences. Each switch has its own row with a short description, and flipping one no longer closes the panel.
Administration
- Notifications on by default for new installs. The three notification kinds start enabled on a new installation. An instance that already saved its choices keeps them: switch the kinds on under Admin → Email → Enabled notifications. Titles stay off, because they pass through the mail server.
- Admin → Email wording says what it means for the whole instance (Enabled notifications, Notification templates), and its Encryption select and template field are readable on the dark theme.
- Administrators' help has a page for every administration tab.
- The deployment notice no longer adds a second scroll bar: it sits beside the sidebar instead of above it.
Upgrading from 2.8.0
- Back up your database. One small database change runs at start.
- Pull the new images (
docker compose pull, thendocker compose up -d). No.envchange is required. - Single sign-on and registration. If you set
OIDC_ALLOWED_DOMAINSand left Allow new registrations off, 2.8.0 created accounts for those domains and 2.8.1 no longer does. Turn registration on to keep that behaviour. An empty domain list now means every domain once registration is on, so list your domains if you want to limit it. - Notification email. An existing instance keeps its saved kinds. Switch them on under Admin → Email if you want them.
Known limits
- Single sign-on. Only Keycloak and Google have been tested. Other providers are expected to work but are unverified.
- Email has been verified with a STARTTLS server; try your own server with Send test email before relying on it.
- Readers of a public assessment or a read-only link do not get live updates; they reload to see changes.
ArgueSecure 2.8.0
ArgueSecure 2.8.0
Email, self-registration, a refreshed look, and a round of security fixes: the application can now send mail (off until you set it up), people can reset their own password, an administrator can let people create their own accounts, and live updates are tightened to the people who should see them.
Sign-in and security
- Security fixes.
- Administrator accounts are never remembered between visits, and the cookies already issued stop working.
- Changing an account's role signs its other devices out.
- Share links are looked up by a hash of the token, so the database never compares the text a visitor types. Existing links keep working.
- Only an assessment's owner, collaborators and administrators join its live channel. Readers of a public assessment or a read-only link reload the page to see changes.
- The websocket accepts connections only from the application's own host (see Upgrading from 2.7.0).
- The sign-in lockout is counted per email address and network address together, and a test now pins that (this was already the behaviour).
- Dependency security updates. Symfony components (HTTP, routing, YAML, MIME) and the spreadsheet library used for imports and exports are updated to versions that fix published advisories. The spreadsheet library now also installs
phpoffice/wmf(MIT). - Forgot password. With email set up, the sign-in page offers a one-time link, good for an hour, to choose a new password. The answer is the same whether or not the address has an account. Using the link ends every session and does not sign anyone in. Deactivated accounts, and non-administrators when sign-in is limited to single sign-on, get no link.
- Self-registration, off by default. An administrator can let people create their own accounts from the Authentication page. It needs working email, because nobody gets an account without following a mailed link, and the person chooses their password only after that. You can limit it to certain email domains and set a daily cap on new accounts. Registered accounts are ordinary, non-administrator accounts that own and belong to nothing.
- Google sign-in is documented alongside the other OpenID Connect providers, with the setup written from Google's documentation. It has not been tested against a live Google account.
The application sends no email until you configure it, and works fully without it.
- Admin → Email takes your SMTP server and sender address, with TLS, STARTTLS or none. Email turns on only after a test message has arrived. The password is stored encrypted.
MAIL_*variables in.envwin over what is stored. - Invitations. Creating an account without typing a password emails the person a one-time link to choose their own. They get a reminder after 3 days and another after 7. You can still have a password generated instead.
- Notification email. Mentions, assignments and drafted summaries can also be emailed. Administrators choose which kinds are allowed, all off by default, and each person can turn them off in their profile. Mail gathers for ten minutes and goes out as one message, with a link and no comment text. Every message ends with a link to stop that kind.
- Editable wording. Each kind of message can be edited, with a preview and a reset to the shipped text.
Administration
- Administrators' help is a separate help area with its own search, visible only to administrators. The administration pages left the public help.
- A deployment notice. Set
APP_NOTICEto show one line of plain text in a band at the top of every page, including the sign-in page. It is not printed. - Moving to another hostname is documented step by step: the proxy, sign-in providers, the websocket origin and what the database does and does not store.
- A deploy-only compose file,
docker-compose.deploy.yml, for a server that has only the file and a.env. A failed image pull now reports the real cause instead of a missing Dockerfile.
Look and feel
- A new look. The application takes on the new brand: palette, fonts, mark and icons.
Upgrading from 2.7.0
- Back up your database. This release adds database changes that run when it starts.
- Check
APP_URL. The websocket now accepts connections only from the host inAPP_URL. If people open the app under another hostname or by IP address, live updates and presence stop for them (the rest of the page works) until you list those hosts inREVERB_ALLOWED_ORIGINS. - Pull the new images and compose file (
docker compose pull, thendocker compose up -d). If you keep your own.env, nothing is required. Optional new lines are in.env.example:MAIL_*,APP_NOTICE,REVERB_ALLOWED_ORIGINS. - Administrators are signed out once. Their remember-me cookies are cleared, and everyone else's sessions continue.
- Email, self-registration and Google sign-in stay off until you set them up.
Known limits
- Single sign-on. Only Keycloak has been tested. Google and other providers are expected to work but are unverified.
- Email has been verified with a STARTTLS server; try your own server with Send test email before relying on it.
- Readers of a public assessment or a read-only link no longer get live updates; they reload to see changes.
ArgueSecure 2.7.0
ArgueSecure 2.7.0
Safer sign-in, scales you define yourself, a trash for deleted assessments,
and a round of improvements to editing and reports.
Sign-in and security
- Two-factor authentication. Anyone can protect their account with an
authenticator app and a set of recovery codes. Administrators can require it
for everyone. - Single sign-on with OpenID Connect. Connect your organisation's identity
provider, then let people sign in with it. New accounts are created only for
the email domains you allow, and administrators can turn password sign-in off
for everyone else. An Authentication page in the admin area holds the
settings and a button to check the connection. Single sign-on is new: it has
been tested against a simulated provider, not yet against a real one, so try
it with yours before relying on it. - Log out other devices now ends exactly the sessions that exist, and
changing your password signs you out everywhere else. - A security event log records sign-ins, failures and administrative
changes. Administrators can download it as CSV or JSON, with filters. - A security review closed a set of smaller findings: exports treat cell
text as text, undo and redo stay within their own assessment, and the
password breach check can no longer block a password change.
Assessments and editing
- A trash for deleted assessments. Restore them, or erase them for good.
Deleted assessments are cleared out automatically after a retention period you
can set. - Your own scales. Administrators define named sets of impact, likelihood
and strength bands and choose one when creating an assessment. - Templates belong to the organisation. Any administrator can create, edit
and delete templates. Publishing an assessment as a template now makes a copy,
so editing one never changes the other. - Warnings before you lose work. Pages with a Save button ask before you
leave with unsaved changes. - Filters in named groups, and a Print menu that asks whether to print
the chart, the list or the report. - Collapsed cards show how many items they hide, and the hover bar no
longer sticks open. - Undo works as expected after a redo, and the dashboard shows the real
totals. - Share links open the assessment straight away for people without an
account.
Reports
- Clearer wording. The cover reports "Current known risk", and defences are
"ranked by cost benefit". - Choose what goes in. Every report section has a switch, the long
appendices start switched off, and model-quality warnings can be left out; the
report says how many it left out. Defences are listed as implemented, planned
and shelved.
Administration
- Importing a spreadsheet now reads what Excel writes, including UTF-16 and
semicolon-separated files. - Generated passwords are shown when you create an account.
- The sidebar shows the version you are running and links to these notes.
- Application logs go to standard error, so
docker compose logsshows
them.
Upgrading from 2.6.3
- Back up your database. This release adds database changes that run when
it starts. - Pull the new images and the new compose file (
docker compose pull,
thendocker compose up -d). The compose file changed: Redis no longer
discards data under memory pressure. - Everyone signs in again once. Sessions now live in the database, so
existing sessions end at the upgrade. If you keep your own.env, copy the
new lines from.env.example. - Templates are converted once. The bundled templates and any template
someone published from their own assessment become shared templates owned by
no one. Published templates are copied, and the original assessments go back
to being ordinary ones with their owners and collaborators unchanged. A
bundled template that was in the trash stays there until an administrator
erases it. - Optional: single sign-on settings (
OIDC_*,OIDC_ALLOWED_DOMAINS) and
SECURITY_LOG_RETENTION_DAYS.
Report links that don't say whether to include the methodology or the warnings
now include neither; before, they included both. The app always sets both, so
only hand-built links and bookmarks change.
Known limits
- Single sign-on has not yet been tried against a real identity provider.
- The browser's Back and Forward buttons and signing out do not warn about
unsaved changes.
ArgueSecure 2.6.3
ArgueSecure 2.6.3
Two more standards templates and a chart fix.
Standards
- NIST CSF 2.0. All 106 Subcategories of the six Functions, as planned
defences under risks and threats, plus a cyber-insurance transfer. Each
cites its control. - EU Cyber Resilience Act. The essential requirements of Annex I and the
manufacturer obligations of Articles 13 and 14, as defences under the risks of
a compromised product, an unhandled vulnerability and enforcement. - Both are also available as control frameworks, so a defence can cite them by
hand.
Fixes
- Chart panels are no longer cut off. Add from template and Suggest on
a card with nothing beneath it, such as a new assessment's root, opened a
panel clipped just below the card. The card now scrolls its panel into view.
Images
Release images are now public packages on the GitHub Container Registry. A
host pulls them without logging in; names and tags are unchanged.
Upgrading from 2.6.2
docker compose pull && docker compose up -d with ARGUESECURE_VERSION=2.6 in
.env. There are no database changes and the compose file is the same.
Templates already loaded stay as they were. The two new templates are
loaded when the first administrator is created, so an existing instance does
not get them by itself. Load them with:
docker compose exec app php artisan db:seed --class='Database\Seeders\SampleContentSeeder' --forceIt creates no users and skips templates that already exist.