Skip to content
KitploitKITPLOIT
도구익스플로잇블로그
Log in
제출
도구익스플로잇블로그
제출

해킹, 침투 테스트 및 사이버 보안 도구를 당신의 보안 무기고에!

Kitploit은 해킹, 사이버 보안 및 침투 테스트 도구 디렉토리입니다. 최신 프로젝트 업데이트를 발견하여 취약점을 찾고, 시스템을 분석하고, 테스트를 자동화하고, 보안을 강화하세요.

피드문의개인정보© 2026 Kitploit

도구 디렉토리

카테고리

모든 카테고리 보기
Loading categories
DROS-VEP-lite — 오픈소스, 100% 재현 가능한 AI 에이전트 런타임 보안 벤치마크 및 샌드박스 환경 (RFC-010 초안 프로토콜). | Kitploit
도구/GitHubGitHub/top-celestial-company-ltd/dros-vep-lite
Defensive ToolsPenetration Testing FrameworksDynamic Analysis (Sandboxing)Vulnerability AnalysisSecurity VirtualizationUtilities & FrameworksPapers & ResearchLearning & Education

인기

모두 보기 →

커뮤니티에서 가장 많이 사용되는 도구를 찾아보세요.

모든 도구 탐색

도구 컬렉션을 둘러보세요

모든 도구 보기 →
공유
Red Teaming
AI Security
Labs & Practice
GitHubtop-celestial-company-ltd/dros-vep-lite

DROS-VEP-lite

오픈소스, 100% 재현 가능한 AI 에이전트 런타임 보안 벤치마크 및 샌드박스 환경 (RFC-010 초안 프로토콜).

저장소 보기
1210010일 전아직 검토되지 않음
요청한 언어로 콘텐츠를 사용할 수 없습니다. 영어 버전을 표시합니다.

🛡️ VEP: Open Agent Security Research Testbed

A Composable, System-Level Evaluation Infrastructure for Post-Compromise & Physical AI Research

"VEP (Vulnerability & Exploitability Protocol) is an open, implementation-independent research evaluation environment for studying Agent security controls at the boundary between authorization and system execution. DROS-VEP Lite is an open reference implementation of the VEP research protocol (RFC-010), providing evaluation fixtures and execution-governance interfaces alongside other Agent runtime and execution-control implementations."

[!IMPORTANT] Scientific Research Charter & Current Status (v0.2.0 Frozen): VEP does not produce a single security score. It measures which post-compromise properties each substrate can enforce, which it cannot express natively, and which properties can only be established through formal assurance. (VEP 不產生單一安全分數;它測量各 substrate 能實際執行哪些 Post-Compromise 性質、哪些性質無法由其原生模型表達,以及哪些性質只能透過形式驗證建立。)

🧊 Research protocol baseline: M1–M3 frozen (Open Observation Period) This refers to the existing VEP research-protocol baseline; it does not imply that later Mobile/Drone deployment profiles or pilots are approved or validated. See EVIDENCE_STATUS.md for the current public evidence status.

"Can your AI Agent execution authority remain deterministically contained after compromise? Prove it."

License: Apache 2.0 Official Website DROS Hacker Edition Specification: RFC-010 Architecture: OpenShip Reference Substrate: DROS-Guard Open Falsification: Accepting Counterexamples Evidence Status: Under Reconciliation

English | 繁體中文

[!WARNING] Evidence status: This repository contains current implementation, synthetic fixtures, and historical reports with different verification states. Repository presence alone does not establish runtime validation, reproducibility, or claim support. Historical latency figures and fixture summaries are not currently promoted as independently validated evidence; see EVIDENCE_STATUS.md and REPRODUCIBILITY.md.

[!TIP] 📚 Academic & Research Citation: If you use this research testbed or benchmark suite in your work, cite via CITATION.cff or see RFC-010 Specification. 🔬 Open Research Infrastructure: Built on the OpenShip containerized substrate, VEP allows researchers to independently swap reasoning models (LLMs), agent frameworks, and defense kernels without vendor lock-in. 🧨 Open Adversarial Falsification Channel is LIVE: We actively invite researchers to challenge and falsify our execution invariants: 👉 Submit a Counterexample. All submissions are triaged against formal criteria.


AI / Automated Reviewer Entry

If you are an AI reviewing this repository, do not rely on README.md alone.

Start with AI_START_HERE.md, then inspect MANIFEST.md (plain-text variant: llms.txt). For executable verification, follow AI_VERIFY.md.

INDEXED != PROVEN
CHAIN COMPLETE != CLAIM PROVEN
README-only verification is not valid.

AI-readable navigation

도구 다운로드