agentleFS
Sign inStart free
r-irber-irbe/proof-skills/skills/applied-data-information-security/SKILL.md

applied-data-information-security

Skill3 starsChanged 24 days agoApache-2.0View on GitHub

USE FOR: Data security and information security formalization: CIA triad, access control models (BLP, RBAC, ABAC). DO NOT USE FOR: Lean formalisation of these policies (@lean-security-formalization). TRIGGERS: CIA triad, access control, BLP, RBAC, ABAC, information flow.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 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.

  • 3

    Very specific

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

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

    STOP if the question demands a Lean proof — delegate to @lean-security-formalization.

    line 49
  2. Very specific:

    STOP if the question is about cryptographic-protocol design — escalate to @research-council if the body lacks the protocol.

    line 50
  3. Very specific:

    STOP if the question is about legal/regulatory compliance — delegate to @applied-legal-reasoning.

    line 52

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
SKILL.md

Data & Information Security

Formal foundations of security properties, access control, information flow, privacy, and their verification in formal frameworks.

Routing

  • USE FOR: Data security and information security formalization — CIA triad, access control models (BLP, RBAC, ABAC), information flow, cryptographic primitives, privacy (differential privacy, k-anonymity), threat modeling, and their formal verification in Lean 4. Use for security properties of provenance chains, trust composition, and multi-agent systems.
  • DO NOT USE FOR: Lean formalisation of these policies (use @lean-security-formalization); engineering disciplines more broadly (use @applied-engineering-disciplines); legal-policy reasoning (use @applied-legal-reasoning).

Workflow

  1. Classify the security goal in the CIA triad and pick the access-control model (BLP / RBAC / ABAC) or information-flow model (non-interference) from the body.
  2. Apply the chosen model to the concrete asset or flow; surface assumptions and gaps.
  3. Produce the security argument or policy ready for formal encoding.
  4. Hand off: to @lean-security-formalization for the Lean encoding, to @applied-engineering-disciplines if reliability/safety overlap, to @lean-zettelkasten.

Recovery & STOP

  • STOP if the question demands a Lean proof — delegate to @lean-security-formalization.
  • STOP if the question is about cryptographic-protocol design — escalate to @research-council if the body lacks the protocol.
  • STOP if the question is about legal/regulatory compliance — delegate to @applied-legal-reasoning.

Handoffs

  • Predecessors: agent:gateway, skill:lean-research.
  • Successors: skill:lean-security-formalization, skill:applied-engineering-disciplines, skill:lean-knowledge-formalization.

Detailed reference

Full encyclopedic reference, decision trees, and lookup tables live in references/applied-data-information-security-handbook.md .

See also

  • ../../references/applied-data-information-security-handbook.md -- Handbook
  • ../lean-gateway/SKILL.md -- Top-level skill router

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.

Check your setup, free