Sitemap
System Weakness

System Weakness is a publication that specialises in publishing upcoming writers in cybersecurity and ethical hacking space. Our security experts write to make the cyber universe more secure, one vulnerability at a time.

AI Security: Guide to Securing AI Systems

11 min read2 days ago

--

Press enter or click to view image in full size
Photo by Andres Siimon on Unsplash

AI is becoming part of almost everything we use today — chatbots, coding assistants, banking systems, customer support, healthcare, and business automation.

But as AI becomes more powerful, it also creates a new security challenge.

How do we secure a system that can learn, generate content, make decisions, and sometimes even take actions on its own?

This is where AI Security comes in.

In this guide, we will understand AI security , including:

  • AI, ML, and Generative AI basics
  • How AI security differs from traditional cybersecurity
  • Prompt injection and jailbreaks
  • LLM security
  • Model and data security
  • Frontend and backend security
  • AI security frameworks
  • Agentic AI security
  • MAESTRO threat modeling
  • A practical AI security architecture example

Let's start from the basics.

1. First, Understand AI, ML, and Generative AI

Before securing AI, we need to understand what we are protecting.

What is AI?

Artificial Intelligence (AI) is the larger concept of machines performing tasks that normally require human intelligence.

Examples include:

  • Understanding language
  • Recognizing images
  • Making decisions
  • Solving problems
  • Learning from information

What is Machine Learning?

Machine Learning (ML) is a part of AI where systems learn patterns from data instead of relying only on manually written rules.

For example, instead of manually writing thousands of rules to detect spam emails, we can train an ML model using examples of:

Spam email → Not spam email

The model learns patterns from the data.

What is Generative AI?

Generative AI is AI that can create new content.

It can generate:

  • Text
  • Images
  • Code
  • Audio
  • Video

Examples include ChatGPT for text, image-generation models such as DALL-E, and coding assistants such as GitHub Copilot.

2. The Three Common Types of Machine Learning

Supervised Learning

The model learns from labeled examples.

For example:

Email → Spam
Email → Not Spam
Email → Spam

The model learns to classify new emails.

Unsupervised Learning

The model works with unlabeled data and tries to discover patterns or groups.

For example, a company could use customer data to discover different customer behavior groups without manually defining those groups.

Reinforcement Learning

The model learns through trial and error.

Good actions receive rewards, while poor actions receive negative feedback.

A simple example is an AI learning how to play a game.

3. What Is an AI Model?

An AI model is the trained system that takes an input and produces an output.

For example:

User Input
↓
AI Model
↓
AI Response

Some common AI models and tools include:

  • GPT / ChatGPT — text generation
  • DALL-E — image generation
  • Codex / GitHub Copilot — code generation

You will also hear two important terms when working with AI:

Token

A token is a small piece of text that an AI model processes.

A token may represent a complete word, part of a word, or sometimes punctuation.

Embedding

An embedding converts information into numbers that represent its meaning or relationships.

This allows AI systems to compare and work with information mathematically.

4. Why AI Security Is Different from Traditional Cybersecurity

This is one of the most important concepts.

Traditional applications are usually deterministic.

That means:

Same Input → Same Output

For example, a calculator will normally return the same result for:

10 + 20

AI systems are different.

They are often probabilistic.

The same question may produce different responses because the output depends on the model, data, context, and other factors.

This creates new security challenges.

Traditional Security

Traditional cybersecurity commonly focuses on:

  • Vulnerable applications
  • Servers
  • Networks
  • Authentication
  • Databases
  • Malware
  • SQL injection
  • Infrastructure vulnerabilities

AI Security

AI security additionally focuses on:

  • Prompt injection
  • Jailbreaks
  • Data poisoning
  • Model manipulation
  • Model extraction
  • Sensitive information leakage
  • Adversarial inputs
  • AI agent abuse

In simple terms:

Traditional security protects applications and infrastructure. AI security protects models, data, AI applications, and the systems connected to them.

5. The Four Core Areas of AI Security

AI security can be divided into four major areas:

1. Model Security

Protect the AI model itself.

2. Data Security

Protect the data used for training, testing, retrieval, and operation.

3. System Security

Protect the complete application around the model, including:

  • Frontend
  • Backend
  • APIs
  • Middleware
  • MCP
  • Databases

4. Governance

Create policies and processes that define how AI should be developed, deployed, monitored, and used.

6. The Jailbreak Problem

One of the easiest ways to understand AI security is through jailbreaking.

A jailbreak happens when someone tries to make an AI system ignore its intended safety rules or restrictions.

For example, an attacker may create a carefully designed prompt that attempts to change the AI’s role or instructions.

The goal could be to make the system:

  • Reveal restricted information
  • Ignore security controls
  • Produce unsafe content
  • Reveal system instructions
  • Perform actions it should not perform

This is why AI applications need security testing beyond normal application penetration testing.

7. What Does an AI Security Engineer Do?

An AI security engineer may work across several activities.

Monitoring and Incident Response

Review security alerts and investigate suspicious AI activity.

Security Testing

Test AI applications for:

  • Prompt injection
  • Jailbreaks
  • Data leakage
  • Model abuse
  • Unauthorized actions

Secure AI Development

Help developers build AI applications with security controls from the beginning.

Threat Intelligence

Track new AI attacks, vulnerabilities, tools, and attacker techniques.

Reporting

Document security findings and explain risks to technical teams and leadership.

AI security is therefore not only about hacking.

It is also about design, monitoring, governance, testing, and risk management.

8. Know Your Enemy: AI Security Frameworks

You do not need to create your own threat list from zero.

Several established frameworks can help.

OWASP Top 10 for LLM Applications

OWASP provides practical guidance around common security risks in applications using large language models.

It is especially useful for developers and security professionals working with LLM applications.

MITRE ATLAS

MITRE ATLAS provides a knowledge base of adversarial tactics and techniques related to AI systems.

It helps security teams understand how attackers may approach AI systems.

NIST AI RMF

The NIST AI Risk Management Framework focuses more broadly on managing AI risks within organizations.

It is useful for security, risk, compliance, and leadership teams.

These frameworks have different purposes.

A strong AI security program can use them together.

9. Securing the AI Model

The first question should be:

Can we trust the model we are deploying?

Three important practices are:

Versioning

Track different versions of your models.

For example:

Model v1.0
Model v1.1
Model v2.0

This helps you understand what changed.

Model Lineage

Know where the model came from.

You should be able to answer questions such as:

  • Who created it?
  • What data was used?
  • Where was it downloaded from?
  • Was it modified?
  • Who approved it?

Governance

Define who has permission to:

  • Create models
  • Modify models
  • Test models
  • Approve models
  • Deploy models

10. Model Security Tools

Two useful open-source tools mentioned in AI security are Garak and ModelScan.

They serve different purposes.

Garak

Garak tests the behavior of a running model.

It can probe for issues such as:

  • Jailbreaks
  • Prompt injection
  • Information leakage
  • Unsafe behavior

Think of it as testing:

“How does this model behave when someone attacks it?”

ModelScan

ModelScan focuses on model files before they are loaded or deployed.

It can help identify potentially malicious content hidden inside model files.

Think of it as:

“Is this model file safe to load?”

A useful approach is:

Model File
↓
ModelScan
↓
Deployment
↓
Running Model
↓
Garak Testing

11. Data Security in AI

Data is one of the most important parts of an AI system.

If the data is compromised, the AI system can also become compromised.

Some important risks include:

Data Poisoning

An attacker inserts malicious or incorrect information into data used by an AI system.

This can affect the behavior of the model.

Model Extraction

An attacker may repeatedly query a model and use the responses to learn about the model or attempt to recreate its behavior.

Metadata Exposure

Sensitive information can accidentally appear in:

  • Files
  • Logs
  • Metadata
  • API responses

Prompt Injection

An attacker places malicious instructions inside input data or content that the AI processes.

12. How Can We Protect AI Data?

Several controls can help.

Privacy-Preserving Technologies

Use technologies that allow data to be processed while reducing unnecessary exposure of sensitive information.

Data Integrity Checks

Verify that data has not been modified or tampered with.

Access Control

Only authorized users and systems should be allowed to access sensitive AI data.

Data Classification

Identify sensitive information before allowing it into AI systems.

Get Rahul’s stories in your inbox

Join Medium for free to get updates from this writer.

For example:

Public Data
↓
Internal Data
↓
Confidential Data
↓
Highly Sensitive Data

Different controls should be applied to different data types.

13. AI Security Checklist

A practical AI security program should consider:

  • Threat modeling
  • Data validation
  • Sensitive-data identification
  • Adversarial testing
  • Rate limiting
  • WAF protection
  • Output filtering
  • Monitoring
  • Model drift detection
  • Unauthorized model changes

Frameworks such as MITRE ATLAS and MAESTRO can also help with threat modeling.

14. Frontend Security

The frontend is where users interact with the AI system.

That also makes it an important attack surface.

A secure AI frontend should consider:

Secure Authentication

Use secure authentication mechanisms such as OAuth 2.0 where appropriate.

Strong Authorization

Make sure users can only access resources they are allowed to access.

Role-Based Access Control

Different users should have different permissions.

For example:

Admin
↓
Full access
Developer
↓
Development resources
User
↓
Limited AI features

Prompt Filtering

Detect and control suspicious inputs before they reach the AI system.

File Upload Protection

If users can upload files, scan them for malicious content.

Rate Limiting

Prevent attackers from sending an excessive number of requests.

Model Extraction Protection

Monitor for unusual patterns such as thousands of automated queries attempting to reproduce model behavior.

Monitoring

Collect useful security telemetry so suspicious activity can be detected early.

15. Backend Security

The backend is where many critical resources live.

This may include:

  • AI models
  • APIs
  • Databases
  • Secrets
  • Business logic
  • User information
  • External integrations

Important security controls include:

Encryption

Protect data both:

  • At rest
  • In transit

Authentication and Authorization

Use strong identity and access controls.

Secrets Management

Never hardcode API keys, passwords, or cloud credentials directly into source code.

Instead, use secure secrets-management systems.

Database Security

Protect databases using:

  • Access controls
  • Encryption
  • Network restrictions
  • Monitoring

Input Validation

Never blindly trust user input.

Secure Logging

Logs should help security teams investigate incidents without unnecessarily exposing sensitive information.

Rate Limiting and Anomaly Detection

Detect unusual traffic and prevent abuse.

Regular Security Testing

Continuously test the application for vulnerabilities.

Data Minimization

A simple rule is:

Do not collect or store data that you do not actually need.

16. What Is the MCP Layer?

Modern AI applications may connect models to tools, APIs, databases, and other external resources.

The middleware / MCP layer can act as the bridge between the AI model and these resources.

For example:

User
↓
AI Application
↓
AI Agent
↓
MCP / Middleware
↓
Tool / API / Database

This layer is extremely important because it controls what the AI can reach.

If an AI agent is given access to a sensitive database or administrative API, a security problem at the agent or middleware layer could have serious consequences.

Therefore, access should follow the principle of least privilege.

17. AI Governance

Technology alone cannot secure AI.

Organizations also need clear policies.

Three important areas include:

NIST AI RMF

Provides a structured approach for managing AI risks.

ISO/IEC 42001

Provides requirements and guidance for an AI management system.

EU AI Act

Provides legal requirements for AI systems based on risk and use cases.

Governance helps organizations answer questions such as:

  • Who can deploy an AI model?
  • What data can AI access?
  • How should AI risks be assessed?
  • Who approves high-risk AI systems?
  • How are AI incidents handled?

18. The New Frontier: Agentic AI

Traditional AI may answer a question.

Agentic AI can take actions.

An AI agent may:

  1. Receive a goal
  2. Plan tasks
  3. Use tools
  4. Access information
  5. Make decisions
  6. Take actions
  7. Continue working based on results

For example, imagine a loan-processing AI agent.

A simple AI system might only calculate a credit score.

An agentic system could potentially:

Receive Application
↓
Collect Documents
↓
Check Information
↓
Call External APIs
↓
Analyze Results
↓
Flag Problems
↓
Recommend a Decision

This provides more automation.

But it also creates more security risks.

The more tools and permissions an agent has, the more important security controls become.

19. Threat Modeling Agentic AI with MAESTRO

Traditional threat-modeling approaches were not designed specifically around modern agentic AI systems.

MAESTRO is a framework designed for threat modeling agentic AI systems.

It looks at an agentic system across seven layers.

The goal is simple:

Instead of looking only at the AI model, examine the entire agentic system layer by layer.

A basic process is:

Step 1 — Describe the System

Understand what the AI agent does.

Create a system architecture and data-flow diagram.

Step 2 — Analyze the Seven Layers

Walk through each layer and identify possible threats.

Step 3 — Document the Threats

For each threat, record information such as:

  • Threat ID
  • Description
  • Mitigation
  • STRIDE category
  • Severity

Step 4 — Choose the Assessment Approach

The assessment can be performed manually or supported by automation tools.

Step 5 — Create the Final Report

Document the architecture, threats, risks, and recommended mitigations.

20. Example: ABC Corporation

Let’s imagine a company called ABC Corporation.

ABC has a cloud-based AI platform that provides agent-driven automation and decision-making for businesses.

Its architecture contains:

  • Firewall
  • Proxy layer
  • Presentation layer
  • Agentic layer
  • Data and services layer
  • API layer
  • External services

A simplified architecture could look like this:

Internet
│
▼
Firewall
│
▼
Proxy Layer
│
▼
Presentation Layer
│
▼
Agentic Layer
┌──────────┬──────────┬──────────┐
│ Agents │ Planning │ LLM │
│ Tools │ Memory │ │
└──────────┴──────────┴──────────┘
│
▼
API / Service Layer
│
┌─────────┴─────────┐
▼ ▼
Databases External APIs

A proper threat-modeling report should include:

  • Project scope
  • Project summary
  • Application architecture
  • Component details
  • Data-flow diagram
  • Identified threats
  • Risk severity
  • Recommended remediation
  • Supporting appendix

This gives security teams a complete view of the system.

21. AI Security Is More Than Prompt Injection

When people hear AI security, they often think only about prompt injection or jailbreaks.

But AI security is much bigger.

You need to protect:

AI SECURITY
│
┌──────────┼──────────┐
│ │ │
Model Data System
│ │ │
└──────────┼──────────┘
│
Governance

And the system around the model includes:

  • Frontend
  • Backend
  • APIs
  • Databases
  • Authentication
  • Authorization
  • Middleware
  • MCP
  • Cloud infrastructure
  • External tools

The model is only one part of the security picture.

22. Final Thoughts

AI security may look complicated at first.

But the basic idea is simple:

Understand what the AI can do, understand what it can access, understand how it can be attacked, and build controls around those risks.

Start with the fundamentals.

Learn:

  • AI and ML basics
  • Generative AI
  • LLM architecture
  • Prompt injection
  • Jailbreaks
  • Data poisoning
  • Model security
  • API security
  • Cloud security
  • Threat modeling

Then learn the major frameworks:

  • OWASP LLM Top 10
  • MITRE ATLAS
  • NIST AI RMF
  • MAESTRO
  • ISO/IEC 42001

Finally, practice in a safe lab environment.

Build a small AI application.

Connect it to an API.

Add authentication.

Add logging.

Then perform security testing.

That is where theoretical knowledge starts becoming practical security experience.

The Future of AI Security

AI agents are becoming capable of performing more real-world tasks.

As AI gets more access to:

  • Company data
  • Cloud infrastructure
  • APIs
  • Databases
  • Business systems
  • External tools

the security requirements will become even more important.

This means AI security will not be only an AI problem.

It will become a combination of:

Cybersecurity + Cloud Security + Application Security + Data Security + AI + Governance.

For security professionals, this creates a new and exciting area to learn.

The best time to start understanding AI security is now.

Key Takeaway

AI security is not about stopping AI.

It is about making AI safer, more trustworthy, and harder to abuse.

If you understand the model, protect the data, secure the surrounding systems, control access, monitor behavior, and use proper threat-modeling frameworks, you can build a much stronger foundation for securing AI systems.

If you found this guide useful, follow for more cybersecurity, AI security, cloud security, and ethical hacking content.AI Security: Guide to Securing AI Systems

System Weakness
System Weakness

Published in System Weakness

System Weakness is a publication that specialises in publishing upcoming writers in cybersecurity and ethical hacking space. Our security experts write to make the cyber universe more secure, one vulnerability at a time.