Scc Security

Organization

RedHatProductSecurity

scc-security

Review OpenShift Security Context Constraints for correct privilege levels. Use when auditing pod security, reviewing SCC assignments, or configuring container runtime permissions on OpenShift clusters.

Overview

Publisher	RedHatProductSecurity
Repository	`prodsec-skills`
Skill name	`scc-security`
Stars	56
Forks	9
Bundled files	Instructions only
License	Apache-2.0
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by RedHatProductSecurity on GitHub. Read the source before you install it.

Installation

Install the Scc Security AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/RedHatProductSecurity/prodsec-skills/tree/main/ge-core/scc-security
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/RedHatProductSecurity/prodsec-skills.git /tmp/prodsec-skills
mkdir -p .claude/skills
cp -r /tmp/prodsec-skills/ge-core/scc-security .claude/skills/scc-security

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Scc Security in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Scc Security on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Scc Security is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

OpenShift Security Context Constraints (SCC)

SCCs control what actions pods can perform and what host resources they can access. If no security context is specified, OpenShift applies the restricted SCC by default.

What SCCs Control

Privileged container execution
Linux capabilities requested by containers
Host directory volume mounts
SELinux context
Container user and group IDs
Host namespace and networking access
FSGroup ownership of volumes
Supplemental groups
Read-only root filesystem requirement
Volume types
Seccomp profiles

SCC Reference

SCC	Description	When to Use
restricted	Denies all host features; requires namespace-allocated UID and SELinux label. Most restrictive.	Default for all workloads; prefer this unless a specific relaxation is justified
nonroot	Like restricted, but allows any non-root UID	When the container must run as a specific non-root UID
anyuid	Like restricted, but allows any UID/GID	When the container requires a specific UID (including root UID without root privileges)
hostnetwork	Allows host networking and ports; requires namespace UID/SELinux	Only for pods that must bind to host network interfaces
hostaccess	Allows all host namespaces; requires namespace UID/SELinux	Only for trusted pods requiring host namespace access
hostmount-anyuid	Like restricted, but allows host mounts and any UID	Only for pods requiring host filesystem access (e.g., persistent volume recycler)
privileged	Full access to all host features; any user, group, SELinux context	Only for cluster administration requiring maximum access
node-exporter	Purpose-built for the Prometheus node exporter	Only for the node exporter DaemonSet
custom	Administrator-defined constraints	Requires careful security review; document every relaxation

Security Review Guidelines

Start from restricted and relax only when a specific capability is justified
Document why a workload cannot run under restricted
Custom SCCs require particular scrutiny: every relaxation from restricted must have a documented rationale
Review that SCCs are bound to the correct ServiceAccounts, not overly broad groups
Verify that no workload uses privileged SCC unless it is a cluster administration component
Check that runAsNonRoot: true is set unless the container requires root to function
Check that readOnlyRootFilesystem: true is set unless the container must write to its root filesystem

Implementation Checklist

All workloads use restricted SCC unless a specific exception is documented
No workload uses privileged SCC without cluster-admin justification
Custom SCCs document every relaxation from restricted
SCC bindings target specific ServiceAccounts, not broad groups
runAsNonRoot: true is set in the pod security context
readOnlyRootFilesystem: true is set in container security contexts
Host path mounts are justified and documented
Host networking is only enabled for pods that require it

Frequently asked questions

What does the Scc Security AI skill do?

Why use Scc Security on TypingMind?

Because you install it once and use it with any model. Scc Security is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Scc Security in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/RedHatProductSecurity/prodsec-skills/tree/main/ge-core/scc-security. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Scc Security?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Scc Security?

As many as you like. As long as a model supports skills, you can use Scc Security with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Scc Security AI skill free?

Yes. It is published on GitHub by RedHatProductSecurity under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Gog

openclaw

OrganizationPopular

Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.

Healthcheck

Audit/harden OpenClaw hosts: SSH, firewall, updates, exposure, backups, disk encryption, gateway security.

Change Impact

Perform evidence-backed impact analysis before changing code, data, interfaces, or governance documents, then compare the planned impact with the actual diff after implementation. Covers call paths,…

Test Collaboration

Inventory and govern a project's test assets. Connect requirements, business rules, risks, bugs, and cross-boundary contracts to stable TEST-IDs and executable evidence in the repository's existing…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

OpenShift Security Context Constraints (SCC)

What SCCs Control

SCC Reference

Security Review Guidelines

Implementation Checklist

References

Frequently asked questions

Related AI Skills

Set up your own AI workspace now