Thoughts on AI, IT, and how KANAP helps CIOs and their teams.
A year after an outage, the auditor or the insurer asks for details. When it started, who decided what, who did what, whether the right parties were notified. An incident register must be able to answer these questions, and it gets you ready for NIS2 at the same time.
Read the article →26.10.7 lets you limit a person to chosen companies or cost centers, in read or edit, everywhere in KANAP. Server clusters now host applications and carry connections. A tour of the release.
Every week brings its share of critical vulnerabilities. The real question is: which ones affect your business applications, and who has to act? KANAP can help, from the published CVE to the recorded decision, including identifying the servers and applications affected.
26.10.6 adds technologies to KANAP, a layer between applications and servers, and vulnerability management. Published vulnerabilities and end of support now reach the business applications they affect. A tour of the release.
Everyone enters amounts in their own currency, KANAP consolidates them in the group's: automatic exchange rates, aligned with your budget rates if you wish, and totals you can trust.
Computed deadlines, recorded renewal decisions, commitments compared with the budget: IT contracts under control in KANAP.
Budget a service the way you buy it, in people, days and prices: KANAP derives the FTE, the cost per FTE and the daily rate, ready for the committee.
Operating and capital spending in one place: IT builds its budget simply, and comes to the review with finance ready.
KANAP now ships in numbered, dated versions, about one a month, with release notes and a documented upgrade. Here is what that gives you, and a tour of the product as it stands today.
Business and cyber criticality, data, recovery plan: classifying every application is the work that comes before any NIS2 effort. A method and a tool, without the spreadsheet.
The infrastructure team keeps Netbox current. KANAP reads it, keeps its asset records in step without retyping, and adds what Netbox does not know: applications, contracts, costs.
The CIO, the project manager, the team lead and the engineer each have their own questions. KANAP's portfolio reports answer them in one click.
Chargeback says who pays; an analytics dimension says what the spend is for: security, cloud, licences. How to use it in the IT budget.
Allocating IT costs across companies and departments with clear, checkable rules, and turning them into chargeback reports.
The reports that get an IT budget through the committee: key figures, trends, chargeback, then freezing the approved version.
Next year's budget from the expected landing: copy what does not change, preview the copy, then rework only the lines that matter.
Firming up the current year's IT budget landing, item by item, so it becomes a solid base for next year's budget.
