From an idea to a deployed security platform for asset monitoring, findings, risk analysis and…

AegisOne — Building a Defensive Cybersecurity & Digital Risk Platform | Phase 1

A strong security approach also requires understanding what assets exist, what security findings are associated with them, how much risk they represent, and how that information can be presented in a centralized and actionable way.

With this idea in mind, I started building AegisOne — an AI-powered cybersecurity and digital risk platform focused on bringing security-related information into one centralized system.

Phase 1 is now complete and live.

This project represents more than just another web application. It is an engineering journey focused on combining software development, backend engineering, cybersecurity concepts, REST APIs, risk analysis, testing, Git/GitHub and cloud deployment into one practical project.

🔐 What is AegisOne?

AegisOne is a defensive cybersecurity and digital risk platform designed around a centralized security dashboard.

The platform provides a foundation for managing and analyzing:

• Security assets
• Security findings
• Risk information
• Risk scores
• Asset status
• Security-related API data
• System health
• Security dashboard insights

The goal is to create a platform where security information can eventually be transformed into meaningful intelligence rather than remaining scattered across different tools and systems.

AegisOne is being developed with a long-term vision of becoming a more advanced security intelligence platform.

Phase 1 establishes the core foundation.

🎯 Why I Started Building AegisOne

While learning cybersecurity and software engineering, I wanted to move beyond tutorials and build something that combines multiple areas of technology into one practical system.

I wanted to understand questions such as:

• How should security assets be represented?
• How can findings be connected to assets?
• How can risk be calculated?
• How should a cybersecurity dashboard communicate information?
• How should a frontend communicate with a backend API?
• How can an application be tested before deployment?
• How can a Python backend be deployed to the cloud?
• How should a project be structured for future expansion?
• How can cybersecurity concepts be integrated with modern software engineering?

Instead of learning each topic separately, I decided to bring them together into one project.

That became AegisOne.

🏗️ Phase 1 — Building the Core Foundation

The first phase focused on creating a functional foundation rather than trying to build every advanced cybersecurity capability immediately.

The major Phase 1 components include:

1. Security Dashboard

AegisOne provides a centralized dashboard designed to present security information in a simple and understandable format.

The dashboard provides visibility into areas such as:

• Total assets
• Critical assets
• High-risk assets
• Average risk
• Security findings
• Open findings
• Recent findings
• Risk distribution
• System status

The idea is to make security information easier to understand from a single interface.

🖥️ 2. Asset Management

Assets are an important foundation of any security platform.

AegisOne currently provides an API-driven asset management layer that supports operations such as:

• Viewing assets
• Creating assets
• Viewing individual assets
• Deleting assets
• Tracking asset type
• Tracking asset target
• Tracking environment
• Tracking security status
• Associating risk information with assets

An asset can represent infrastructure such as a server or another security-relevant target.

Example asset information can include:

Name: Production Server Type: Server Target: IP address / target Environment: Production

This structure provides a foundation for more advanced asset intelligence in future phases.

⚠️ 3. Security Findings

AegisOne also introduces a findings layer.

Security findings represent issues or observations that may require investigation or remediation.

Each finding can contain information such as:

• Finding title
• Severity
• Status
• Associated asset
• Description

The platform can therefore move toward a workflow where security teams can identify findings, associate them with assets, understand their severity and eventually track remediation.

📊 4. Risk Analysis

One of the important components of AegisOne is its risk-analysis foundation.

The platform represents security risk using a numerical score and a corresponding risk level.

The current Phase 1 risk model provides levels such as:

• Critical
• High
• Medium
• Low

The system evaluates a risk score and maps it to a corresponding level.

For example, the Phase 1 demonstration model uses thresholds for:

80+ → Critical

60–79 → High

30–59 → Medium

Below 30 → Low

This is intentionally a foundational model.

The long-term objective is to evolve this into a much more sophisticated risk engine that can incorporate multiple security signals rather than relying on a simple demonstration score.

🔌 5. REST API

The backend of AegisOne is built around a REST API architecture.

The current API includes endpoints for:

Health

GET /health

Used to verify that the API service is operational.

API Information

GET /api/info

Provides information about the AegisOne API.

Assets

GET /api/assets/

Retrieves available assets.

GET /api/assets/{asset_id}

Retrieves an individual asset.

POST /api/assets/

Creates a new asset.

DELETE /api/assets/{asset_id}

Removes an asset.

Risk

GET /api/risk/

Provides the risk overview.

POST /api/risk/{asset_id}

Performs risk calculation for an asset.

Findings

GET /api/findings/

Retrieves security findings.

This API-first approach makes it possible for the frontend and future applications or services to communicate with AegisOne through defined interfaces.

⚙️ Technology Stack

AegisOne combines several technologies that I have been working with while developing my software engineering and cybersecurity skills.

Backend

• Python
• FastAPI
• Pydantic
• REST APIs
• Uvicorn

Frontend

• HTML
• CSS
• JavaScript

Development & Version Control

• Git
• GitHub
• VS Code

Testing

• Pytest
• FastAPI/Starlette testing tools

Deployment

• Render
• Cloud-hosted frontend
• Cloud-hosted backend/API

The project is structured so that additional components can be introduced without having to rebuild the entire platform from scratch.

🧩 System Architecture

At a high level, the Phase 1 architecture follows this flow:

User

↓

AegisOne Web Dashboard

↓

REST API

↓

Backend Application

↓

Asset / Finding / Risk Logic

↓

Security Information

The frontend communicates with the backend through HTTP API requests.

This separation between frontend and backend provides a foundation for future improvements such as additional security services, authentication, databases, analytics and AI-powered components.

🖼️ The Dashboard

The dashboard is designed around the idea of a Security Risk Command Center.

Instead of presenting raw technical information alone, the interface organizes information into different sections:

Dashboard

Provides an overall security overview.

Assets

Provides asset visibility and asset management.

Findings

Provides security finding information.

Risk

Provides risk-related information and risk distribution.

System

Provides information about the API and system connectivity.

This structure was intentionally designed to make the platform expandable.

🧪 Testing & Quality

Building a project is not only about making the application run.

Testing was an important part of Phase 1.

The AegisOne backend was tested using pytest, covering areas including:

• Root endpoint
• Health endpoint
• Asset retrieval
• Asset creation
• Missing asset handling
• Findings retrieval
• Risk overview
• Risk calculation
• Invalid risk endpoint handling

The final test run achieved:

9 tests passed

This gave me confidence that the core Phase 1 API functionality was behaving as expected before and during deployment.

☁️ Production Deployment

After developing and testing the application locally, I moved the project to a cloud deployment environment.

AegisOne now has:

Live Frontend

https://aegisone-frontend.onrender.com

Production API

https://aegisone-rngk.onrender.com

API Documentation

https://aegisone-rngk.onrender.com/docs

The backend also exposes a health endpoint that can be used to verify service availability.

This deployment stage was especially valuable because deploying a project introduces a different set of engineering considerations compared with running everything locally.

🐙 Open Source Development

AegisOne is publicly available on GitHub.

GitHub Repository:

https://github.com/samirlevate8788-creator/AegisOne

The repository contains the main project components, including:

• Backend
• Frontend
• AI engine structure
• Security engine structure
• Database structure
• Docker configuration
• Documentation
• Tests
• Project configuration

The repository is designed to provide a foundation for continued development.

📁 Project Structure

The project currently follows a structure similar to:

AegisOne

• .github/
• ai-engine/
• backend/
• database/
• docker/
• docs/
• frontend/
• security-engine/
• tests/
• .dockerignore
• .gitignore
• README.md
• docker-compose.yml
• requirements.txt

This structure separates different responsibilities and keeps the project ready for future expansion.

🧠 Engineering Challenges

Building AegisOne also involved solving several practical engineering problems.

Some of the challenges included:

Frontend ↔ Backend Communication

The frontend originally needed to communicate with a locally hosted API.

Moving the application to production required changing the architecture so that the frontend could communicate with the cloud-hosted API.

This introduced considerations such as:

• API base URLs
• CORS
• Production configuration
• Cloud deployment
• API availability

Backend Structure

During development, I experimented with different backend structures and routing approaches.

This helped me understand the importance of:

• Clear project organization
• Modular architecture
• Dependency management
• Correct Python imports
• API routing
• Maintainable code structure

Testing Before Deployment

Another important lesson was that deployment should not be the first time an application is tested.

Running the automated test suite before deployment helped identify issues early and gave a repeatable way to validate the core API.

Cloud Deployment

Moving from localhost to a real cloud environment introduced another layer of engineering.

The project had to account for:

• Production API URLs
• CORS configuration
• Service health
• Deployment configuration
• Frontend/API separation
• Cloud service limitations

These practical problems taught me as much as writing the original code.

🔐 Security Philosophy

AegisOne is designed as a defensive cybersecurity platform.

The objective is to help organize and analyze security information rather than facilitate offensive or harmful activity.

The platform's long-term direction is focused on areas such as:

• Security monitoring
• Risk analysis
• Vulnerability management
• Asset intelligence
• Security findings
• Threat intelligence
• Security analytics
• AI-assisted security analysis

Security is treated as a continuous process rather than a single feature.

🚧 What Phase 1 Does NOT Claim

One of the most important lessons from this project is understanding the difference between a working foundation and a fully mature enterprise security product.

Phase 1 establishes the core platform and demonstrates the architecture, API layer, dashboard, asset management, findings, risk-analysis foundation, testing and deployment.

It should not be interpreted as a replacement for mature enterprise security products or a complete autonomous security operation.

Advanced capabilities require significantly more development, testing, security validation, infrastructure and real-world data.

That is exactly why AegisOne is being developed in phases.

🚀 Phase 2 — Coming Soon

Phase 1 is complete.

The next stage is Phase 2.

The goal of Phase 2 is to move AegisOne from a core security platform foundation toward a more advanced security intelligence system.

Potential areas of development include:

🤖 AI Security Intelligence

Exploring AI-assisted analysis for security information and findings.

🧠 Advanced Risk Engine

Moving beyond basic risk scoring toward a more comprehensive risk model using multiple security signals.

🔎 Security Scanning

Expanding the platform toward deeper security assessment and scanning capabilities within a controlled defensive framework.

📈 Advanced Analytics

Introducing richer security dashboards, trends, historical analysis and visualization.

🖥️ Asset Intelligence

Expanding asset information and improving asset-level security visibility.

⚠️ Advanced Findings Management

Improving finding prioritization, tracking and security workflows.

👤 Authentication & Access Control

Introducing stronger identity, authentication and role-based access mechanisms as the platform evolves.

🗄️ Persistent Database Layer

Expanding beyond the Phase 1 foundation toward durable production data storage and more scalable data management.

🛡️ Production Hardening

Improving security controls, validation, error handling, configuration management, monitoring and overall platform reliability.

These are future development goals, not claims that all of these capabilities already exist in Phase 1.

🌱 What I Learned From Building AegisOne

The biggest takeaway from this project is that building real software is very different from simply writing code.

A project goes through many stages:

Idea → Architecture → Development → Testing → Debugging → Deployment → Validation → Improvement

Every stage brings different challenges.

Through AegisOne, I gained practical experience with:

• Backend development
• REST API design
• FastAPI
• Python
• Frontend development
• JavaScript
• API integration
• CORS
• Git/GitHub
• Automated testing
• Cloud deployment
• Project architecture
• Documentation
• Cybersecurity concepts
• Risk analysis
• Debugging production issues

Most importantly, I learned how different technical areas connect to form a complete system.

💡 Learning by Building

AegisOne is part of a larger approach I am following in my development journey:

Learn → Build → Break → Debug → Improve → Deploy

Instead of only collecting technologies and certifications, I want to understand how those technologies work together in real projects.

That means working with:

Programming

Systems

Software Engineering

Cybersecurity

Artificial Intelligence

Cloud & Deployment

This combination is becoming an important part of the direction I want to take as an engineer.

📌 Current Status

AegisOne Phase 1

STATUS: COMPLETE & LIVE

Current Phase 1 foundation includes:

✅ Security dashboard ✅ Asset management ✅ Security findings ✅ Risk analysis foundation ✅ REST API ✅ API documentation ✅ Automated testing ✅ GitHub repository ✅ Cloud deployment ✅ Project documentation

Phase 2

STATUS: COMING SOON

The next phase will focus on deeper security intelligence, advanced analysis and stronger platform capabilities.

🔗 Project Links

🌐 Live Platform: https://aegisone-frontend.onrender.com

⚙️ Production API: https://aegisone-rngk.onrender.com

📚 API Documentation: https://aegisone-rngk.onrender.com/docs

💻 GitHub Repository: https://github.com/samirlevate8788-creator/AegisOne

👨‍💻 Built & Led By

Samir Levate

Founder & Project Lead

AegisOne

B.Tech Computer Science & Engineering Student

I am currently focused on strengthening my skills across:

Software Engineering | Systems Programming | Operating Systems | AI | Cybersecurity | Full-Stack Development

I believe in learning by building real systems, understanding fundamentals deeply and continuously taking on more challenging engineering problems.

🚀 Final Thoughts

AegisOne started as an idea to build something practical around cybersecurity and software engineering.

Phase 1 transformed that idea into a working, tested and deployed platform foundation.

But this is only the beginning.

The next challenge is to make AegisOne smarter, more scalable and more capable of turning security data into meaningful intelligence.

Phase 1 is live.

Phase 2 is coming soon.

Building today. Securing tomorrow.