Merilane Underwriter Kit — practice Credit / Escalate / Deny ($29 on merilane.io)
Paste a wrong-charge ticket → get Credit, Escalate, or Deny. Buy the Kit on merilane.io.
Clouvel AI
Grok Bot ISSO/GRC companion that drafts RMF, FedRAMP, and CMMC artifacts, checks official sources, and can optionally watch your stack.
ISSACHAR (ISSO Support for Security Assessment, Compliance, Hardening, Authorization, and Risk) is a Grok Bot companion for ISSOs, ISSMs, GRC analysts, assessors, and the engineers who work with them. Call it "Issy," short for ISSACHAR (ISS-a-kar). Version 1.0, Nov 2026.
It explains and drafts NIST RMF, DoD/DoW authorization, FedRAMP, CMMC and CUI, and private-sector GRC work (CSF 2.0, ISO 27001, SOC 2, PCI DSS, HIPAA, SEC, NYDFS). It does not replace the ISSO or the Authorizing Official; it works for them.
From a sanitized system, finding, interconnection, or stack, it reasons from mission need and threat to control intent, options, compensating measures, and residual risk. It can draft SSP implementation statements, POA&M or FedRAMP Accepted Weakness entries, risk-acceptance memos, ISA/MOU outlines, one-page AO briefs, and engineer tickets, each marked "DRAFT - requires ISSO review." It speaks assessor and engineering language, and will say when absolute security would break the mission.
Before stating a fast-moving program's status, it checks the official source when the web is available, or tells you to verify. Exact control text is fetched when possible and otherwise labeled a paraphrase. Licensed standards (PCI DSS, CIS Controls, ISO 27001, SOC 2, CSA CCM) are discussed by area or family in ISSACHAR's own words, never by copying their text.
An optional threat watch, offered in getting-started setup and not pre-enabled, can check the CISA KEV catalog, BOD 26-04 rules, vendor and GitHub advisories, and end-of-support lists, then alert only on matches to a general stack you describe. No connectors are required. Web access is optional, for source checks and the watch. Single-user license; do not share or repost the share link. Updates, if offered, come as notes or a new version that adds a separate bot, not an automatic update.
Because this is a digital template delivered instantly as a Grok share link, all sales are final once you receive access, except where the law requires otherwise. If the link doesn't work or the product doesn't match this listing, contact me through Capabase and I'll fix or replace it.
Disclaimer: advisory aid only, not legal advice; no guarantee of compliance or ATO. The human ISSO/AO decides. Verify against official sources. Never paste classified information, CUI, or PII. Not affiliated with xAI, NIST, DoW/DoD, FedRAMP, CISA, or the Cyber AB.
Input
Walk me through categorizing a moderate-impact internal web app on a major cloud, no CUI, for a federal civilian agency. What RMF path follows?
Output
A categorization discussion pointing to FIPS 199 moderate, the likely baseline, and the next RMF steps, with official source citations and items marked for the ISSO to confirm.
Input
Draft an SSP implementation statement for AC-2 from this sanitized description: cloud identity provider, role-based access, quarterly access review. Flag what I still need to confirm.
Output
A "DRAFT - requires ISSO review" AC-2 statement covering who, what, how, how often, and where evidence lives, with placeholders for organization-defined values and a list of gaps.
Recommended so official sources and threat feeds can be checked live. If the web is unavailable, the bot should say so and avoid stating program status from memory alone.
The shared Grok Bot template, Version 1.0, Nov 2026: role and instructions, the isso-getting-started first-run setup, and these skills: isso-governing-principles, isso-rmf-authorization, isso-artifacts, isso-fedramp-cmmc-cui, isso-security-architecture, isso-interconnections-api, isso-emerging-tech, isso-enterprise-crosswalks, and isso-threat-watch.
Typical drafts, always marked for human review: SSP implementation statements, POA&M or FedRAMP Accepted Weakness entries, risk-acceptance memos, ISA/MOU outlines, one-page AO briefs, engineer-ready tickets, evidence request lists, and stack-relevant KEV and BOD briefings. It also helps with interconnections and API security, identity and SaaS attack paths such as help-desk resets, AI and agentic AI security, and incident-reporting clocks.
The optional threat watch is a skill plus a getting-started offer to create a recurring check. It is not pre-enabled. No connectors are included or required.
License: one purchase covers one user. Do not share, repost, or resell the share link. Contact the seller for a team license. Because this is a digital template delivered instantly as a Grok share link, all sales are final once you receive access, except where the law requires otherwise. If the link doesn't work or the product doesn't match this listing, contact me through Capabase and I'll fix or replace it.
If updates are offered, they may come as notes or a new version. Adding a new version creates a separate bot. It does not automatically update a copy you already added.
ISSACHAR is an advisory aid, not a compliance platform or system of record, and not a path to an ATO.
No reviews yet.
Input
Our contract mentions CUI and DFARS 7012. What CMMC level should I plan for, and what is the current public program status?
Output
A current-status check from official sources, or an "as of / verify" caveat if the web is unavailable, plus a plain-language CMMC-level discussion and what still depends on the contract.
Input
Here is a general stack, no CUI: RHEL 9, Windows Server 2022, Kubernetes on a major cloud, a named firewall vendor. Which KEV items and BOD 26-04 due dates actually apply?
Output
Matches only, each labeled for applicability (for example FCEB, contractor, or private sector), with computed BOD 26-04 timing and the live KEV due date when available.
Updated Sep 28, 2026
Creator
Wallwatch Labs