Skip to content

v1.5.0
Compare
Choose a tag to compare
@noamblitz noamblitz released this 01 Feb 14:29
v1.5.0
a4c8a78
This commit was created on github.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

https://docs.openkat.nl/release_notes/1.5.html

OpenKAT 1.5: multi organization support

The main feature of the 1.5 release of OpenKAT is the ability to scan multiple organizations from one OpenKAT instance and manage the data and users for each of them. It comes with an API to automatically deploy organizations and users from an external source.

This gives you the ability to manage OpenKAT for a large group of organizations while maintaining the separation of data and users for each of them. It also allows you to supply credentials to users within those organizations and to give them access to their own data, make reports etc.

In addition to this several other features have been added that support this use case, such as the ability to filter and manage and add objects in bulk and add scanning and inheritance of scan levels from a higher level. They were requested by some of our large scale partners and we will continue working on such features in the forthcoming releases.

Features:

  • Most importantly, this is the first version of KAT that offers fully implemented multi-organization support. New organizations can be added in the Rocky admin interface (/admin), after which databases in xtdb and KAT-alogus will be automatically added. Clients can be added for each organization that cannot view data of other organizations
  • Certificates can now be created without having a relation to a website
  • IPAddresses now inherit a scan level from a netblock if that netblock is known
  • NMAP can now scan ip ranges
  • Rocky now offers bulk actions for the deletion of OOIs and giving clearance levels to OOIs
  • Rocky now offers filtering options based on clearance levels and clearance level types

IMPORTANT

This feature includes a new version of XTDB. Therefore, the env setting XTDB_TYPE has to be set to xtdb-multinode. Also, all data in xtdb will be lost and cannot be moved to this version. If you use a locally installed version, you can change to the xtdb version in this repo: https://github.com/dekkers/xtdb-http-multinode.

Full Changelog

Coordination

What's Changed

New Contributors

Full Changelog: v1.4.0rc1...v1.5.0rc2

Octopoes

What's Changed

New Contributors

Full Changelog: minvws/nl-kat-octopoes@v1.4.0rc1...v1.5.0rc2

Bytes

What's Changed

New Contributors

Full Changelog: minvws/nl-kat-bytes@v1.4.0rc1...v1.5.0rc2

Boefjes

What's Changed

New Contributors

Full Changelog: minvws/nl-kat-boefjes@v1.4.0...v1.5.0rc2

Rocky

What's Changed

New Contributors

Full Changelog: minvws/nl-kat-rocky@v1.3.0...v1.5.0rc2

Mula

What's Changed

New Contributors

Full Changelog: minvws/nl-kat-mula@v1.4.0rc1...v1.5.0rc2

Contributors

dekkers, jpbruinsslot, and 12 other contributors
Assets 4
Loading