ISMS

Compliance that doesn't die the day after the audit. Open-source, AI-first management system.

[ISMS @isms_sh]

@kidtsang You too buddy, keep it coming! :)

[ISMS @isms_sh]

@kidtsang Yes and consistency, so important :)

[ISMS @isms_sh]

Security is the answer. Risk management is the question.
Skip the question and you spend forever answering the wrong one.
#InfoSec #GRC #ISO27001 #Europe

[ISMS @isms_sh]

Adding your suppliers to your ISMS should be this simple:

from isms import IsmsClient

client = IsmsClient.from_env()

client.suppliers.add({
"name": "Anthropic",
"supplier_type": "saas",
"criticality": "high",
"data_access": True,
"confidentiality": 5, "integrity": 4, "availability": 4,
"notes": "Claude API. SOC 2 Type II, GDPR DPA with SCCs.",
})

pip install isms-sdk, set two env vars, run, each supplier lands in the register with an identifier, CIA classification, and a full audit trail.

Just opened a PR adding this as a runnable example https://t.co/78v0X4dNFK

#ISMS #GRC #ISO27001 #InfoSec #Python

[ISMS @isms_sh]

A compliance tool your team actually opens beats a "complete" one they dread.

So we slimmed every register in ISMS: the tall stat-card grids that pushed your list off-screen are now a single click-to-filter strip. Counts stay glanceable, the list comes back above the fold.

Small polish, daily payoff.

#ISMS #GRC #ISO27001 #InfoSec #UX

[ISMS @isms_sh]

100%, enforcement without visibility is just a black box with rules.
For us the single write path is what makes it transparent: every change lands as a versioned git commit + an audit entry, so what changed, by whom, and why is always inspectable. Enforcement and transparency end up being the same feature, not a trade-off.

Appreciate the sharp point 🙏

[ISMS @isms_sh]

ISMS v0.7.0 is out.

The theme: trust in your data. Every register now flows through one enforced write path — the UI, the CLI, and AI-agent suggestions all hit the same validation, status, and audit trail. No path bypasses the rules.

Also in 0.7.0:
- Richer reviews: @-mention teammates, word-level table diffs
- Cloudflare Access SSO with just-in-time provisioning
- Smoother self-hosting + a fuller change-management CLI
- Registers and reviews now work on mobile
- Programs is its own register, with consistent status everywhere

Plus a companion: the official Python client.

pip install isms-sdk

Self-hosted, git-backed, yours.

https://t.co/bJzZeoLHYp

#infosec #compliance #ISO27001 #opensource #Python

[ISMS @isms_sh]

"The vendor passed our security review" is a sentence about the past.

The review is a snapshot. The breach tends to happen in the months after — questionnaire filed, everyone moved on. Third-party risk isn't a form you complete once a year; it's a posture you keep watching.

#TPRM #infosec #compliance #ISO27001 #cybersecurity

[ISMS @isms_sh]

@joovier_ Manage your risks and suppliers, because the risks are not going anywhere https://t.co/L4OLyUs2eM.

[ISMS @isms_sh]

isms-python is live on PyPI, the official Python client for ISMS.

Your information security management system shouldn't be something you only touch through a web UI. Now you can program it: seed registers, automate audits, and build your own dashboards, against a cloud instance on https://t.co/9oR1HEUpFM or your own self-hosted deployment.

pip install isms-sdk

from isms import IsmsClient
client = IsmsClient.from_env()
client.suppliers.add({
"name": "Acme SaaS",
"supplier_type": "saas",
"criticality": "high",
})

Your data, your rules, git-backed, API-first, self-hostable. Installs as `isms-sdk`, imports as `isms` (like sentry-sdk).

Repo: https://t.co/Y3W5tWGCDu
PyPI: https://t.co/x5KiTsHGZV

#Python #infosec #compliance #ISO27001 #opensource

[ISMS @isms_sh]

@H4r5h_T4nd37 @Qualityworld @IRCAofficial @BSIIndia Well done , and so the journey begins :)

[ISMS @isms_sh]

A quiet truth about incident management:

The team that logs 50 "minor" incidents a quarter is in better shape than the one that logs 3.

Not because it has fewer problems, because it can actually see them. The near-miss you don't record is the post-mortem you'll write next year.

#incidentmanagement #infosec #ISO27001 #resilience #grc

[ISMS @isms_sh]

@Guronnimo .sh for techies ;)

[ISMS @isms_sh]

@Anastasis_King Too many tools :D

[ISMS @isms_sh]

@Shubham_pen Great explanation thanks :)

[ISMS @isms_sh]

@shoguncarroll Information Security Management System :).

[ISMS @isms_sh]

ISMS is self-hosted & git-backed: your ISO 27001 / SOC 2 docs are just markdown in your own repo. clone → edit → sync. Full version history, full data sovereignty.

#ISO27001 #GRC #infosec #compliance #selfhosted

[ISMS @isms_sh]

A silent audit trail is worse than none.

If your logging can fail without anyone noticing, you don't have an audit trail — you have a hope. The entity changes, the record doesn't, and you find out during the
audit, not before.

Make governance writes fail loud. A gap you can see beats a gap you can't.

#ISO27001 #ISMS #GRC #compliance #infosec

[ISMS @isms_sh]

@Sarakhan49309 The intelligent ISMS system https://t.co/L4OLyUs2eM