Skip to main content

Topic in the Kopexa blog

ISMS

Build, operate and improve an ISMS: explore guides, examples and practical answers on information security.

More on this topic

20–28 of 49

GuideGuides & How-To

Exporting ISMS data: How to test your future exit

Before buying software, check whether risks, measures, evidence and their relationships can leave with you. Includes a practical export test and acceptance record.

Julian Köhn·
NewsPrivacy & Engineering

Sungrow: Who can control your equipment remotely?

The fixed iSolarCloud vulnerability illustrates an operational risk: central remote access to many installations. Review access, dependencies and fallback operation.

Julian Köhn·
GuideGuides & How-To

Introducing GRC software: Who takes responsibility for what?

A role model for GRC implementation: distinguish decision-makers, business owners and administrators, then test the handover to daily operations.

Julian Köhn·
GuideGuides & How-To

ISMS risk review: When do you need to reassess?

Identify changes, new information and ineffective safeguards, review your risk assessment and keep decisions traceable.

Julian Köhn·
GuideGuides & How-To

ISMS management review: How do you prepare decisions?

Turn ISMS reports into a basis for decisions: show action needed, resources, owners and verifiable follow-up.

Julian Köhn·
NewsPrivacy & Engineering

The phishing email comes from a real colleague. What now?

A compromised business mailbox makes the sender credible. Organise containment, investigation and a controlled return to work.

Julian Köhn·
GuideGuides & How-To

ISMS pilot project: Test the workflow, not just the interface

Assess ISMS software using a real case: hand over responsibility, replace evidence and follow an open measure through to a decision.

Julian Köhn·
GuideGuides & How-To

ISMS metrics: How do you measure effectiveness rather than tasks?

A green task status does not prove a safeguard works. Define ISMS metrics with a clear measurement question, data source and action rule.

Julian Köhn·
OpinionGuides & How-To

Risk acceptance: Accepted does not mean finished

An accepted risk remains a risk. Document the decision, authority, conditions and reassessment triggers so acceptance stays defensible.

Julian Köhn·