paulvandenbraken

We have not seen the "exploding lists" anymore: closure is ok!

Hi Madelon, We now have content in the all-organisations crisis room. At this moment for most of the organizations we now see a findings dashboard in the organisation-specific crisisroom. However...

In Octopoes zien we in de logging: 691879 [error] Failed recalculating scan profiles [org=spou] [dur=4.65s] Traceback (most recent call last): File "/opt/venvs/kat-octopoes/lib/python3.11/site-packages/octopoes/tasks/tasks.py", line 109, in recalculate_scan_profiles octopoes.recalculate_scan_profiles(datetime.now(timezone.utc)) File "/opt/venvs/kat-octopoes/lib/python3.11/site-packages/octopoes/core/service.py", line...

We have internally closed this issue (199) for the OpenKAT-project because it cannot be reproduced anymore.

@stephanie0x00 Alle drie de boeven staan aan (zie email 9-9). Clearance level is 2

Kennisnet prefers having the ability in both bullets 1 and 3: First one will report on compliance on NCSC's TLS-policy Bullet 3 for the reason you explained yourself.

It should be nice to have a clear definition of "finding" and "vulnerability". The expectation is that all critical-, high- and (at the end) medium-risk notifications should be reported for...

@underdarknl That's not the case since this only occurs for this one organization and for all other organizations it simultaniously works without these error-loggings (octopoes can be reached). Any clue...

Ik have tried to clone on our acceptance env. this morning, resulting in this error and the included tracktrace: Apr 08 11:48:23 openkat-acc-fe01 kat-rocky[1291]: 2025-04-08T09:48:23.112309 [info] Cloning organization settings event_code=910000...

this is the new stacktrace: [2025-06-19 11:16:16 +0200] [1518] [ERROR] [session] 2025-06-19T11:16:16.936962 [error] An error occurred: 'NormalizerConfigInDB' object has no attribute 'settings'. Rolling back session [2025-06-19 11:16:16 +0200] [1518] [ERROR]...