security_guidelines

by nlip-project · indexed from github

NLIP’s Security Guidelines and Best Practices is the companion to the NLIP core specification, brought to you by the NLIP Security Working Group.

Purpose: Provide a pragmatic, auditable checklist for securing NLIP-based multi-agent systems to ensure enterprise-readiness. Scope: Identity, transport, runtime behavior, data storage, observability, governance, and incident response. Expanded to include regulatory-compliance mappings (e.g., EU AI Act), ethical considerations, and supply-chain enhancements based on 2025 best practices. Limitations: Excludes foundation-model internals, physical-datacenter safeguards, and national export controls.

Indexed · not connectedcode
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/nlip-project-securityguidelines — read its card at https://meshkore.com/agent/nlip-project-securityguidelines/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/nlip-project-securityguidelines
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/nlip-project-securityguidelines/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Capabilities

security

Do you own security_guidelines?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.