Update README.md
Browse files
README.md
CHANGED
|
@@ -1,10 +1,83 @@
|
|
| 1 |
---
|
| 2 |
-
|
| 3 |
-
|
| 4 |
-
|
| 5 |
-
|
| 6 |
-
|
| 7 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 8 |
---
|
| 9 |
|
| 10 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
---
|
| 2 |
+
language: en
|
| 3 |
+
tags:
|
| 4 |
+
- ai-security
|
| 5 |
+
- llm-security
|
| 6 |
+
- agentic-ai
|
| 7 |
+
- red-teaming
|
| 8 |
+
- adversarial-ml
|
| 9 |
+
- governance
|
| 10 |
+
- risk-management
|
| 11 |
+
- safety
|
| 12 |
+
- cybersecurity
|
| 13 |
+
license: apache-2.0
|
| 14 |
---
|
| 15 |
|
| 16 |
+
# Cogensec
|
| 17 |
+
|
| 18 |
+
Cogensec builds security and governance for agentic AI systems.
|
| 19 |
+
|
| 20 |
+
We treat AI as decision-making infrastructure, not just software.
|
| 21 |
+
That means securing identity, intent, memory, autonomy, and trust across models, tools, and multi-agent workflows.
|
| 22 |
+
|
| 23 |
+
## What you’ll find here
|
| 24 |
+
|
| 25 |
+
We publish practical artifacts for builders, researchers, and security teams:
|
| 26 |
+
|
| 27 |
+
- **Security evaluation suites** for LLMs and agentic workflows
|
| 28 |
+
- **Adversarial datasets** for testing misuse, jailbreaks, prompt injection, and tool abuse
|
| 29 |
+
- **Reference agents** and **defensive patterns** (guardrails, policies, enforcement primitives)
|
| 30 |
+
- **Research notes and reproducible experiments** focused on real-world deployment risks
|
| 31 |
+
- **Governance templates** and guidance aligned to modern AI risk frameworks
|
| 32 |
+
|
| 33 |
+
## Our focus areas
|
| 34 |
+
|
| 35 |
+
- **Agent security**: tool misuse, agentic escalation, multi-agent coordination risks
|
| 36 |
+
- **Non-human identity**: authentication, authorization, and lifecycle for agents and tools
|
| 37 |
+
- **Memory governance**: retention, leakage, poisoning, and policy enforcement
|
| 38 |
+
- **Intent and control**: goal integrity, autonomy boundaries, and safe orchestration
|
| 39 |
+
- **Trust and provenance**: context integrity, auditability, attestation, and monitoring
|
| 40 |
+
|
| 41 |
+
## How to use our work
|
| 42 |
+
|
| 43 |
+
- Start with pinned repositories for the most current releases.
|
| 44 |
+
- Each repo includes:
|
| 45 |
+
- installation and quickstart
|
| 46 |
+
- evaluation methodology
|
| 47 |
+
- dataset/model cards where applicable
|
| 48 |
+
- reproducibility notes and limitations
|
| 49 |
+
|
| 50 |
+
## Responsible use
|
| 51 |
+
|
| 52 |
+
Cogensec publishes security research to improve safety in AI systems.
|
| 53 |
+
Some materials may describe adversarial behavior to support testing and defense.
|
| 54 |
+
|
| 55 |
+
- Use responsibly and ethically.
|
| 56 |
+
- Don’t deploy findings to harm others or evade safeguards.
|
| 57 |
+
- Report issues or concerns through the contact channels below.
|
| 58 |
+
|
| 59 |
+
## Contributing
|
| 60 |
+
|
| 61 |
+
We welcome:
|
| 62 |
+
- issue reports with reproduction steps
|
| 63 |
+
- benchmark proposals and test cases
|
| 64 |
+
- dataset improvements and labeling fixes
|
| 65 |
+
- PRs that improve documentation and reproducibility
|
| 66 |
+
|
| 67 |
+
If you want to collaborate on research or run joint evaluations, reach out.
|
| 68 |
+
|
| 69 |
+
## Contact
|
| 70 |
+
|
| 71 |
+
- Website: cogensec.com
|
| 72 |
+
- Email: tarique@cogensec.com
|
| 73 |
+
- GitHub: github.com/requie
|
| 74 |
+
|
| 75 |
+
## Citation
|
| 76 |
+
|
| 77 |
+
If you use Cogensec artifacts in research, please cite the relevant repository.
|
| 78 |
+
Where provided, use the `CITATION.cff` file.
|
| 79 |
+
|
| 80 |
+
## License
|
| 81 |
+
|
| 82 |
+
Unless stated otherwise, repositories here are released under the **Apache-2.0** license.
|
| 83 |
+
Datasets may have their own terms, always check the dataset card.
|