ISMS Copilot 2.0 has been created in September 2025. We barely released it, so, there are still a lot of things we can improve.
We believe in being upfront about what's working well and what needs improvement. Whether you’re a customer or considering using our tool, we believe you should do it knowing that not everything’s perfect.
This page lists issues we're actively working to resolve in ISMS Copilot 2.0.
If you encounter any of these problems, know that we're aware and on it. If you spot something not listed here, please report it at https://tally.so/r/3qJb2G or https://app.ismscopilot.com/help.
Issue: The assistant sometimes references ISO/IEC 27001:2013 controls instead of the current 2022 version.
Why it happens: We're migrating our knowledge base from v1 to v2, and some legacy 2013 mappings still surface in responses.
Status: Actively working on this. Our priority is completing the knowledge base migration to ensure all control references use the 2022 standard.
Workaround: Cross-reference responses with official ISO 27001:2022 documentation. You can also add the correct 2022 controls to your workspace's "Custom knowledge" section.
Issue: The assistant sometimes interprets legitimate corrections or questions about inconsistencies as attempts to override its core guidelines, triggering unnecessary warning messages.
Why it happens: Our safety guardrails are currently too sensitive and can misinterpret constructive feedback as jailbreak attempts.
Status: Tuning the guardrails to be less rigid and more receptive to user feedback.
Workaround: If you get an override warning, try rephrasing your correction or question. We're collecting examples to improve this.