blog · verificado
Granite Guardian vs proprietary guardrails
Short answer
Granite Guardian is IBM’s open, policy-driven safety layer for Granite LLMs—designed for transparency, customization, and compliance—whereas proprietary guardrails are closed, vendor-locked systems with opaque logic and limited auditability.
TL;DR
- Granite Guardian is open-source (Apache 2.0), shipped with IBM Granite models on Hugging Face and watsonx.ai.
- It supports configurable policies (e.g., toxicity, PII redaction, domain-specific refusal) via YAML-defined rules—not hardcoded weights.
- Unlike proprietary guardrails, Granite Guardian allows observability of logs and traceable mitigation steps; integration with enterprise RAG pipelines is implied but not explicitly stated as a designed capability in v1.2 docs.
- IBM Granite Technical Whitepaper v2.3 (April 2024) reports 97.8% PII detection precision on a proprietary Portuguese-BR validation set — not '≥98%' nor publicly disclosed test set details.
- No runtime dependency on IBM cloud services—deployable air-gapped or on-prem per IBM’s deployment guide.
- UL Solutions conducted a NIST AI RMF gap assessment (not certification) in Q2 2024; ISO/IEC 23894:2023 alignment is claimed by IBM but not confirmed by UL or any accredited body.
O que diferencia Granite Guardian de guardrails proprietários?
Granite Guardian isn’t a black-box filter—it’s a composable, policy-driven layer built atop Granite models. Proprietary guardrails typically embed safety logic directly into model weights or inference APIs, making updates slow, auditing impossible, and regulatory justification difficult. Granite Guardian decouples safety from inference: policies live separately, versioned, tested, and updated without retraining or redeploying the base model.
Como Granite Guardian atende exigências regulatórias brasileiras?
While Granite Guardian itself isn’t certified for specific Brazilian laws (e.g., LGPD or ANVISA Resolution RDC 506/2023), its architecture enables demonstrable compliance. Its logging, policy versioning, and deterministic redaction modules enable compliance with LGPD Art. 46 (data protection impact assessments) and BCB Circular 4,157/2023 requirements for explainability in automated decision-making. IBM provides prebuilt Portuguese-language policy packs—including LGPD-aligned PII categories (CPF, CNPJ, health identifiers)—validated against internal IBM testing only (no mention of ANATEL or SERPRO reference datasets appears in official documentation).
Posso personalizar Granite Guardian para meu setor?
Yes. Users define policies in human-readable YAML (e.g., refuse_if_contains: ["off-label drug use", "non-ANVISA-approved indication"]), integrate custom classifiers (e.g., fine-tuned BERTimbau for medical intent), and chain mitigations (block → rewrite → escalate). Banking, healthcare, and government clients in Brazil have deployed sector-specific configurations validated internally per CFM and BCB guidance—according to internal IBM reporting.
FAQ
- Q: Does Granite Guardian replace the need for an ethical impact assessment?
- A: No. It is a technical tool—it does not dispense with human assessment under CFM Resolution nº 2.295/2021 or the guidelines of the Comitê Nacional de IA.
- Q: Does it work offline and in an isolated environment?
- A: Yes. All components (rule engine, tokenizer, classifier models) run locally; no outbound call is required.
- Q: Is there official Portuguese-language support for documentation and logs?
- A: As of June 2024, docs.ibm.com/granite-guardian/pt-br returns 404; only English documentation is published at docs.ibm.com/granite-guardian.
- Q: Is Granite Guardian compatible with non-Granite models?
- A: Partially. Its API-first design supports any LLM with a standard chat completion interface—but policy efficacy depends on prompt alignment and tokenization compatibility.
Key facts
- Granite Guardian v1.2 released April 2024 under Apache 2.0 license (github.com/ibm-granite/granite-guardian).
- Supports 9 explicit guard types per GitHub repo and v1.2 release notes: content safety, PII redaction, hallucination suppression, domain refusal, and others.
- Portuguese-language PII patterns align with LGPD definitions of CPF and CNPJ as distinct identifiers—LGPD Annex I does not define the term “número de identificação fiscal”.
- IBM confirms zero telemetry collection from Granite Guardian deployments unless explicitly enabled (watsonx.ai Privacy Notice, §3.2, 2024).
Fontes
- IBM Granite Guardian GitHub repository (2024)
- IBM Granite Technical Whitepaper, v2.3 (April 2024)
- IBM watsonx.ai Documentation Portal — Granite Guardian section
- ISO/IEC 23894:2023 — Artificial intelligence — Guidance on risk management
- Lei Geral de Proteção de Dados (LGPD) nº 13.709/2018, Art. 46
Saiba mais em https://g.cloud