Document least privilege model as alternative to SYSDBA for Oracle co…

[brandonwest-netwrix]

clarify actual Oracle Data collection permissions

Gives writers a lower-privilege option for Oracle data collection instead of requiring the SYSDBA role.

Generated with AI

[github-actions]

Auto-Fix Summary

4 issues fixed, 4 skipped across 2 files

Category	Fixes
Substitutions	2
Dale: passive-voice	2

Skipped (needs manual review)	Reason

| docs/accessanalyzer/11.6/requirements/databases/oracle/oracle.md:47 — Dale: xy-slop | 'Only applies to Windows Servers and not on Linux or Unix operating systems' is a positive-first scoping clarification, not the 'x is not y, x is z' negative-first reversal the rule targets; rewriting risks changing the intended scope. |
| docs/accessanalyzer/11.6/requirements/databases/oracle/oracle.md:50 — Dale: wordiness | 'There is a least privilege model for scanning your domain.' is mildly wordy, but a concise rewrite risks altering meaning or creating redundancy with the preceding bullet. |
| docs/accessanalyzer/12.0/requirements/databases/oracle/oracle.md:47 — Dale: xy-slop | 'Only applies to Windows Servers and not on Linux or Unix operating systems' is a positive-first scoping clarification, not the 'x is not y, x is z' negative-first reversal the rule targets; rewriting risks changing the intended scope. |
| docs/accessanalyzer/12.0/requirements/databases/oracle/oracle.md:50 — Dale: wordiness | 'There is a least privilege model for scanning your domain.' is mildly wordy, but a concise rewrite risks altering meaning or creating redundancy with the preceding bullet. |

Ask @claude on this PR if you'd like an explanation of any fix.

[github-actions]

Documentation PR Review

Editorial Review

docs/accessanalyzer/11.6/requirements/databases/oracle/oracle.md

• Clarity — Line 46: "Recommmended" is misspelled (three ms). Suggested fix: "Recommended".
• Clarity — Line 46: The bullet offers two options joined by "OR", but the bolded Recommended label sits at the front of the whole bullet, so the reader can't tell which option is recommended — the SYSDBA role, the least privilege model, or both equally. Add punctuation after the label and attach it to a single option. Suggested fix: "- Recommended: User with the SYSDBA role. Alternatively, use the Oracle Target Least Privilege Model."
• Clarity — Line 46: Uppercase "OR" reads as a code or logic operator. Nothing else in this document uses uppercase conjunctions. Suggested fix: lowercase "or", or split the alternative into its own sentence as above.
• Structure — Line 46: The new link duplicates the pointer to the same page in the sentence immediately below (lines 50–52), so the reader meets the same destination twice in four lines. Either drop the link from the bullet and let the following paragraph carry it, or drop the paragraph and keep only the bullet.
• Consistency — Line 46: The new link text is "Least Privilege Model" while the existing link to the same page (line 51) is "Oracle Target Least Privilege Model". Use the page's own title in both places. Suggested fix: "Oracle Target Least Privilege Model".
• Completeness — Line 46: The bullet introduces the least privilege model as a peer alternative to SYSDBA without saying what the trade-off is, so the reader has to open another page to make the choice. Add a short clause naming the trade-off — for example, whether any scan capability is reduced under the least privilege model.
• Clarity — Line 56: "Open the following firewall ports:" is an imperative introducing four reference lists grouped by data collector, so it reads as an instruction to open every port listed rather than only those for the collectors in use. Suggested fix: "Open the following firewall ports for each data collector you use:".

docs/accessanalyzer/12.0/requirements/databases/oracle/oracle.md

Same changes as the 11.6 file, so the same findings apply:

• Clarity — Line 46: "Recommmended" is misspelled (three ms). Suggested fix: "Recommended".
• Clarity — Line 46: The bolded Recommended label applies to the whole bullet, so it's ambiguous which of the two options — SYSDBA role or least privilege model — is the recommended one. Suggested fix: "- Recommended: User with the SYSDBA role. Alternatively, use the Oracle Target Least Privilege Model."
• Clarity — Line 46: Uppercase "OR" reads as a logic operator and is inconsistent with the rest of the document. Suggested fix: lowercase "or", or split into a separate sentence.
• Structure — Line 46: The new link duplicates the pointer to the same page on line 51. Keep one of the two.
• Consistency — Line 46: Link text "Least Privilege Model" conflicts with "Oracle Target Least Privilege Model" on line 51 for the same destination. Use the page title in both.
• Completeness — Line 46: The least privilege model is offered as an alternative with no stated trade-off, forcing the reader off the page to decide. Add a clause naming what differs between the two options.
• Clarity — Line 55: "Open the following firewall ports:" introduces four collector-specific lists, so the imperative implies the reader should open all of them. Suggested fix: "Open the following firewall ports for each data collector you use:".

Line 9 in both files ("lets you audit and monitor") is a clean improvement over "provides the ability to" — no issue.

Summary

14 editorial suggestions across 2 files (7 per file — the two files received identical changes). Vale and Dale issues are auto-fixed separately.

---

What to do next:

Comment @claude on this PR followed by your instructions to get help:

• @claude fix all issues — fix all editorial issues
• @claude help improve the flow of this document — get writing assistance
• @claude explain the voice issues — understand why something was flagged

You can ask Claude anything about the review or about Netwrix writing standards.

Automated fixes are only available for branches in this repository, not forks.

[github-actions]

Auto-Fix Summary

6 issues fixed, 2 skipped across 2 files

Category	Fixes
Dale: passive-voice	2
Dale: spelling	2
Dale: wordiness	2

Skipped (needs manual review)	Reason

| docs/accessanalyzer/12.0/requirements/databases/oracle/oracle.md:47 — Dale: wordiness | 'Only applies to Windows Servers and not on Linux or Unix operating systems' could be tightened, but any rewrite also has to resolve the 'applies to ... and not on' preposition mismatch and the scope of 'Windows Servers'; the tighter phrasings risk narrowing the author's intended meaning. |
| docs/accessanalyzer/11.6/requirements/databases/oracle/oracle.md:47 — Dale: wordiness | 'Only applies to Windows Servers and not on Linux or Unix operating systems' could be tightened, but any rewrite also has to resolve the 'applies to ... and not on' preposition mismatch and the scope of 'Windows Servers'; the tighter phrasings risk narrowing the author's intended meaning. |

Ask @claude on this PR if you'd like an explanation of any fix.