MTA-7036: adding requirements for ISO-42001

[anarnold97]

---

JIRA

• MTA-7036

---

DESCRIPTION

• Adds a new concept module, con_ip-protection-model-hosting.adoc, to the Developer Lightspeed LLM configuration chapter to address the ISO/IEC 42001 (Controls A.5.1 and A.10.4) compliance gap identified in MTA-7036.

The module covers:

• A disclosure that Developer Lightspeed transmits source code snippets intact to the configured LLM provider, with no automatic sanitization

• An [IMPORTANT] advisory on the IP and data privacy risks of using public SaaS-based LLM endpoints (such as public OpenAI or Azure OpenAI) with proprietary codebases

• Recommendations to use Red Hat OpenShift AI or Red Hat Enterprise Linux AI (RHEL AI) as self-managed, on-premise alternatives for organizations with strict IP policies, regulatory constraints, or air-gapped environments
  Guidance on configuring a private endpoint in both standalone and centralized configuration management modes

• The module is included in assembly_configuring_llm.adoc ahead of the provider configuration reference so users see the advisory before selecting an endpoint.

---

PREVIEW

• 3.1. Data privacy, intellectual property protection, and model hosting considerations
  • 3.1.1. Red Hat Developer Lightspeed for MTA code transmission to the LLM
  • 3.1.2. Recommended mitigation: Self-managed model hosting
  • 3.1.3. Configuring Red Hat Developer Lightspeed for MTA to use a private endpoint

Summary by CodeRabbit

• Documentation
  • Added guidance for configuring LLM analysis with IP protection and model hosting options.
  • Documented privacy considerations when sending code snippets to external AI providers, including the fact that snippets are not automatically redacted.
  • Added recommendations for using self-managed AI platforms and private OpenAI-compatible endpoints, along with configuration guidance and credential-handling reminders.

[coderabbitai]

Warning

Review limit reached

@anarnold97, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 58 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 1b0f1b2a-7bed-4d2e-be2c-bafce744719d

📥 Commits

Reviewing files that changed from the base of the PR and between 3b0e893 and 3bbe2e2.

📒 Files selected for processing (2)

• docs/topics/developer-lightspeed/assembly_configuring_llm.adoc
• docs/topics/developer-lightspeed/con_ip-protection-model-hosting.adoc

📝 Walkthrough

Walkthrough

A new AsciiDoc topic documents IP/data privacy considerations for {mta-dl-plugin} LLM usage and private endpoint configuration, and the configuring-LLM assembly includes that topic and clears its context attribute afterward.

Changes

IP Protection and Model Hosting Documentation

Layer / File(s)	Summary
New IP protection topic and assembly inclusion docs/topics/developer-lightspeed/con_ip-protection-model-hosting.adoc, docs/topics/developer-lightspeed/assembly_configuring_llm.adoc	Creates the new topic covering unredacted code transmission, public SaaS endpoint warnings, supported self-managed AI platforms, and private OpenAI-compatible endpoint configuration. The assembly includes the topic and unsets configuring-llm at the end.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Possibly related PRs

• migtools/mta-documentation#324: Adds related centralized LLM-proxy configuration documentation in the same {mta-dl-plugin} LLM configuration area.

Suggested reviewers: djzager, fabianvf

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title matches the ISO-42001 compliance-focused documentation changes, even though it is broader than the specific model-hosting content.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

🧹 Nitpick comments (1)

docs/topics/developer-lightspeed/con_ip-protection-model-hosting.adoc (1)

25-36: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Consider expanding "AI" on first general use.

Line 30 uses "AI platforms" as a general term. Red Hat documentation style typically expands "artificial intelligence (AI)" on first use unless it appears in a product name. Consider:

-Organizations with strict intellectual property (IP) protection requirements, regulatory constraints, or air-gapped network environments should deploy a self-managed LLM instance and configure {mta-dl-plugin} to route all queries to that private endpoint. This approach ensures that source code snippets never leave your controlled infrastructure.
+Organizations with strict intellectual property (IP) protection requirements, regulatory constraints, or air-gapped network environments should deploy a self-managed LLM instance and configure {mta-dl-plugin} to route all queries to that private endpoint. This approach ensures that source code snippets never leave your controlled infrastructure.
 
-Red{nbsp}Hat supports the following on-site and self-managed AI platforms for this purpose:
+Red{nbsp}Hat supports the following on-site and self-managed artificial intelligence (AI) platforms for this purpose:

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/topics/developer-lightspeed/con_ip-protection-model-hosting.adoc` around
lines 25 - 36, Expand the first general use of “AI” in the “Recommended
mitigation: Self-managed model hosting” section so it reads “artificial
intelligence (AI)” before using the abbreviation, while leaving product names
like {ocp-name} AI and RHEL AI unchanged. Update the surrounding prose in the
developer-lightspeed topic so the term is introduced in a style-consistent way
without altering the product-specific names or links.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@docs/topics/developer-lightspeed/con_ip-protection-model-hosting.adoc`:
- Around line 25-36: Expand the first general use of “AI” in the “Recommended
mitigation: Self-managed model hosting” section so it reads “artificial
intelligence (AI)” before using the abbreviation, while leaving product names
like {ocp-name} AI and RHEL AI unchanged. Update the surrounding prose in the
developer-lightspeed topic so the term is introduced in a style-consistent way
without altering the product-specific names or links.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: fb57f172-34a2-4640-af05-c45bdaa10fa2

📥 Commits

Reviewing files that changed from the base of the PR and between a22f4a0 and d5ae878.

📒 Files selected for processing (2)

• docs/topics/developer-lightspeed/assembly_configuring_llm.adoc
• docs/topics/developer-lightspeed/con_ip-protection-model-hosting.adoc

[Pkylas007]

Looks great, thanks!

[Pkylas007]

LGTM, thank you!

[rromannissen]

This is PERFECT! Thank you!

[mpershina]

Left some suggestions, mostly based on the concept content requirements. Let me know if you have any questions/concerns.