Web Application Security

Organization

RedHatProductSecurity

web-application-security

Review web application security controls against OWASP-aligned risks. Use when building, auditing, or reviewing server-side web applications that handle user input, sessions, authentication, or access control.

Overview

Publisher	RedHatProductSecurity
Repository	`prodsec-skills`
Skill name	`web-application-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 Web Application 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/web-application-security
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/RedHatProductSecurity/prodsec-skills/tree/main/ge-core/web-application-security

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

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/web-application-security .claude/skills/web-application-security

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

Use it in TypingMind

Enable Web Application 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 Web Application 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 Web Application 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.

Web Application Security

Vulnerability Classes

Category	Threats
Input validation	Command injection, SQL injection, Cross-Site Scripting (XSS)
Upload handling	Local File Inclusion (LFI), Remote File Inclusion (RFI)
Session management	Man-in-the-Middle (MITM), session fixation, session hijacking
Data exposure	Cleartext data theft, insecure storage, cache leaks
Authentication	Credential stuffing, brute force, account enumeration
Access control	Privilege escalation, IDOR, missing function-level checks

Security Requirements

Server-Side Controls

All security controls MUST be implemented server-side. Client-side validation is a UX convenience, not a security boundary. This applies to:

Input validation and sanitization
Upload type and size restrictions
Authentication and session management
Authorization decisions

Network-Level Protections

Deploy a Web Application Firewall (WAF) in front of public-facing applications where feasible
Enable DDoS protection on Internet-facing endpoints
Terminate TLS at the edge; enforce HTTPS end-to-end

CORS

Configure Cross-Origin Resource Sharing to allow only known, explicitly listed origins
Never use wildcard (*) origins on endpoints that accept credentials
Validate the Origin header server-side before reflecting it

CSRF Protection

Enable framework-provided CSRF token mechanisms (e.g., Django CSRF middleware, Spring CSRF, Rails protect_from_forgery)
Use SameSite cookie attributes as a defense-in-depth layer
Verify tokens on every state-changing request

Session Management

Generate a new session ID after successful authentication (prevent session fixation)
Never expose session IDs in URLs
Store session tokens in secure, HttpOnly, SameSite cookies
Invalidate sessions on logout, idle timeout, and absolute timeout
Bind sessions to client fingerprint where feasible (IP, User-Agent)

Sensitive Data Handling

Encrypt sensitive data in transit (TLS 1.2+) and at rest
Do not store sensitive data longer than necessary
Disable caching for responses containing sensitive data (Cache-Control: no-store)
Never log passwords, tokens, or PII

Authentication Hardening

Implement multi-factor authentication for privileged or Internet-facing accounts
Use uniform error responses for login, registration, and credential recovery to prevent account enumeration (e.g., "Invalid credentials" regardless of whether the username exists)
Enforce account lockout or progressive delays after repeated authentication failures

Access Control

Adopt least-privilege and deny-by-default for every request
Route all requests through a centralized access-control verification layer
Enforce authorization on direct object references; never rely on obscurity of IDs
Re-validate privileges on long-lived sessions

Implementation Checklist

References

OWASP Input Validation Cheat Sheet
OWASP CSRF Prevention Cheat Sheet
OWASP Transport Layer Security Cheat Sheet
OWASP Proactive Controls: Protect Data Everywhere
OWASP Proactive Controls: Enforce Access Controls

Frequently asked questions

What does the Web Application Security AI skill do?

Why use Web Application Security on TypingMind?

Because you install it once and use it with any model. Web Application 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 Web Application Security in TypingMind?

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

Which AI models can use Web Application 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 Web Application Security?

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

Is the Web Application 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

Add Model Provider

openclaw

OrganizationPopular

Add and live-prove a model provider with non-interactive config one-liners, without exposing credentials.

Diagnose Gateway

Diagnose Gateway, config, secrets, channels, and port failures with read-only one-liners.

Apple Notes

Create, view, edit, delete, search, move, or export Apple Notes via the memo CLI on macOS.

Bear Notes

Create, search, and manage Bear notes via grizzly CLI.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Web Application Security

Vulnerability Classes

Security Requirements

Server-Side Controls

Network-Level Protections

CORS

CSRF Protection

Session Management

Sensitive Data Handling

Authentication Hardening

Access Control

Implementation Checklist

References

Frequently asked questions

Related AI Skills

Set up your own AI workspace now