agentleFS
joaoguimaraesprojoaoguimaraespro/personal-finance/.cursor/rules/csharp-security.mdc

personal-finance / rules

Cursor rule1 starsChanged todayMITView on GitHub

C#/.NET security: secrets, SQL injection, validation, JWT auth and authorisation, safe errors

The file

We split this csharp-security.mdc into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    No keys, tokens or connection strings in source or appsettings*.json.

    line 12
  2. Very specific:

    Use the framework handlers (AddAuthentication().AddJwtBearer(...)), never hand-parsed tokens.

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 6,809 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
csharp-security.mdc
---
description: "C#/.NET security: secrets, SQL injection, validation, JWT auth and authorisation, safe errors"
globs: **/*.cs,**/*.csproj,**/appsettings*.json
alwaysApply: false
---
<!-- Generated by armature from stack-dotnet/rules/csharp/security.md. Edit the source rule, not this file. -->
# C# security

Extends [common/security.md](common-security.mdc).

## Secrets
- No keys, tokens or connection strings in source or `appsettings*.json`. User secrets locally, environment or a
  secret manager deployed. Read required settings with a fail-fast check at startup.

## Input
- Validate requests at the boundary (FluentValidation in a pipeline behaviour, or explicit guards) before business
  logic runs. Validate sort fields and filter operators against an allow-list before composing dynamic queries.
- Parameterised SQL only (EF Core, Dapper parameters, ADO.NET parameters).

## Authentication and authorisation
- Use the framework handlers (`AddAuthentication().AddJwtBearer(...)`), never hand-parsed tokens.
- JWT bearer: validate issuer, audience (the service's own client id, never `account`), lifetime and signing key;
  `MapInboundClaims = false` so claim names stay as issued.
- Authorise at the endpoint or handler with policies; tenant and roles come from validated token claims, not from
  headers, query strings or routes.
- SignalR over WebSockets reads the token from `access_token` only on hub paths.

## Errors
- Clients get Problem Details with a safe message and an error code; logs get the exception with structured
  context. Never return stack traces, SQL or file paths. Never log raw tokens, passwords or personal data.

<!-- Adapted from affaan-m/ECC rules/csharp/security.md (MIT) at d2ef268 (identical to the Ordo frozen copy); merged with NEXUS knowledge/keycloak (audience per service, realm roles) and knowledge/dotnet/signalr. -->

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.