AI Model Security Core Components
AI Model Security enables you to have flexible controls to secure, validate, and
manage AI models across different sources through Security Groups,
Sources, Rules, and Scans.
AI Model Security delivers a comprehensive framework to establish and enforce
security standards for AI models across your organization. Unlike traditional
security tools that simply scan for malware, AI Model Security recognizes that AI
models require more nuanced security considerations that incorporate license
validation, file format verification, and context-specific security checks based on
the teams and environments using the models.
The AI Model Security approach moves beyond the simplified first-party versus
third-party model distinction to provide granular security controls that scale with
enterprise needs. This approach centers around four key components: Security
Groups, Sources, Rules, and Scans.
| Entity | Description | Examples |
| Security Groups | Serve as the foundation of your AI Model Security posture,
allowing you to combine specific rules and requirements for models
from a particular source. |
- HuggingFace-Research
- S3-Production
- Partner-S3-Audit
|
| Source | Each Security Group is assigned to a specific Source,
which represents where model artifacts reside, such as Hugging Face
for external models or Local Storage and Object Storage for internal
models. The source designation is crucial as it provides metadata
that powers specific security rules applicable to models from that
source. |
|
| Rules | Within each Security Group, you configure Rules that
define the specific evaluations performed on models. Rules can
verify proper licensing, check for approved file formats, scan for
malicious code, and detect architectural backdoors. Each Rule can be
enabled or disabled and configured as blocking or non-blocking,
giving you precise control over which security issues prevent model
usage versus those that simply generate warnings. |
- License Existence Check
- Serialization Format Safety
- Author Verification
- Malicious Backdoor Detection
|
| Scan | When models are evaluated against these Rules, a Scan is
performed, documenting the verdict across all rules. These Scans
create an audit trail of security evaluations and serve as decision
points to either promote secure models forward or block potentially
threatening ones early in your workflow. Here's what a typical
scan will look like:
| Scan of fraud-detector:v2.1.0 using S3-Production group |
AI Model Security leverages rules to help organizations establish sophisticated,
scalable security frameworks tailored to their specific requirements. This flexible
approach enables teams to enforce strict blocking mechanisms for high-severity
threats while maintaining non-disruptive alerting for compliance monitoring—allowing
security teams to effectively manage risk without hindering developer productivity.
The result delivers dual benefits: end users gain confident access to vetted models
through a seamless experience, while security teams receive comprehensive protection
for their AI/ML infrastructure.
To implement AI Model Security effectively, you'll typically need at least two
Security Groups: one for external models using Hugging Face as a Source, and another
for internal models using Local or Object Storage Sources. This separation allows
you to apply appropriate security standards based on the origin and intended use of
models across your organization.