Skip to tutorial content
Rate module Not yet rated

Reviewing the Commands a Pattern Runs

4 min read
On this page

In this lesson, you will learn:

  • Why review pattern commands
  • How to list them
  • How they tie to the privilege matrix

🔁 Quick look back: Last time: Debugging a Pattern. You learned how to debug a pattern step by step.

1 The Problem: Security Asks ‘What Exactly Runs on Our Servers?’

Farah asks for the exact commands Discovery runs. A vague answer isn’t enough because:

  • Security must approve what runs.
  • sudo rules must match those commands.

🎯 The problem: Security wants to know exactly what runs on SNWR’s servers.

👉 The fix: List the commands from the patterns, review them, and tie them to the privilege matrix.

Table of commands and needs.
Figure 1. Part of the pattern command review.

2 Listing commands

Pattern Designer can show the commands a pattern runs, depending on your release. You can also read them from the steps, or from Debug output.

💡 Good to know: Keep the list per pattern. When content updates, check whether commands changed.

3 Reviewing them

  • Every command should only read.
  • Commands needing sudo go into the sudo list.
  • Commands needing an app login use the app credential.

💡 Good to know: Need a refresher? See Client Prerequisites › Building the Service Account and Privilege Matrix for the matrix itself.

4 Project Clear View: How We Implemented It

📍 Situation: Farah asked for the exact commands.

🧭 Decision: List them per pattern and review them with her.

🛠️ Steps we took:

  1. Listed commands for the Linux, Windows and PostgreSQL patterns.
  2. Marked which need sudo or an app login.
  3. Checked each against the privilege matrix.
  4. Reviewed the list with Farah.

✅ What we verified:

  • Every command only reads.
  • Farah approved the list.

📁 Evidence: The command list, attached to the privilege matrix.

5 Quick recap

  • Security needs to know what runs on servers.
  • List commands per pattern.
  • Tie them to sudo rules and app credentials.
  • Recheck after content updates.

6 Check yourself

Think of your answer first. Then tap to check.

1 Why review pattern commands? Show answer

Security must approve what runs, and sudo rules must match.

2 What should every Discovery command do? Show answer

Only read.

3 When should you recheck the list? Show answer

After pattern content updates.

Nice work! SNWR knows exactly what Discovery runs. 🎉
Next up: The Customization Decision: Do We Really Need a Custom Pattern?

Was this lesson helpful?

Have a question or doubt?

Ask here and get help from instructors and fellow learners.

0 / 300

Only logged-in learners can post.