<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: CHIDURALA SAI PAVANI</title>
    <description>The latest articles on DEV Community by CHIDURALA SAI PAVANI (@chidurala_saipavani_b17a).</description>
    <link>https://dev.to/chidurala_saipavani_b17a</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3898837%2Ffb8b1cdc-df87-439e-bda2-ce2832d00db1.png</url>
      <title>DEV Community: CHIDURALA SAI PAVANI</title>
      <link>https://dev.to/chidurala_saipavani_b17a</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/chidurala_saipavani_b17a"/>
    <language>en</language>
    <item>
      <title>Building ProShield-AI: How MongoDB Atlas Powers a Real-Time Cybersecurity Platform</title>
      <dc:creator>CHIDURALA SAI PAVANI</dc:creator>
      <pubDate>Thu, 30 Apr 2026 09:56:09 +0000</pubDate>
      <link>https://dev.to/chidurala_saipavani_b17a/building-proshield-ai-how-mongodb-atlas-powers-a-real-time-cybersecurity-platform-2b9g</link>
      <guid>https://dev.to/chidurala_saipavani_b17a/building-proshield-ai-how-mongodb-atlas-powers-a-real-time-cybersecurity-platform-2b9g</guid>
      <description>&lt;p&gt;By Chidurala Sai Pavani,&lt;br&gt;
khajamoinuddin, J.Sirisha, Kalluri Vishal Reddy.&lt;/p&gt;

&lt;p&gt;Developed under the guidance of Professor &lt;a class="mentioned-user" href="https://dev.to/chanda_rajkumar"&gt;@chanda_rajkumar&lt;/a&gt; ,&lt;br&gt;
and we are thankful for his valuable support throughout this project.&lt;/p&gt;

&lt;p&gt;When we began working on ProShield-AI, the idea seemed straightforward: build a system that could detect suspicious activity and help analysts respond faster.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fpnobx5z5rwa50u1x5fev.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fpnobx5z5rwa50u1x5fev.png" alt=" "&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;But very early into development, we encountered a challenge that quietly sits behind every cybersecurity system — data.&lt;/p&gt;

&lt;p&gt;Not just large volumes of data, but data that is inconsistent, unpredictable, and constantly evolving. Every log carried a different structure, a different level of detail, and sometimes an entirely new format.&lt;/p&gt;

&lt;p&gt;At that point, the problem was no longer just about detecting threats. It became about designing a system that could handle this kind of data without breaking.&lt;/p&gt;

&lt;p&gt;The Nature of Cybersecurity Data&lt;/p&gt;

&lt;p&gt;In a typical application, data is structured and predictable. In cybersecurity, it rarely is.&lt;/p&gt;

&lt;p&gt;A simple log might look like this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"source_ip"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"192.168.1.15"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"activity"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"failed_login"&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;

&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;But another event from the same system might include additional attributes:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"source_ip"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"10.0.0.25"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"activity"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"malware_detected"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"file_hash"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"xyz"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"severity"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"high"&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Over time, new fields appear, formats change, and the volume increases rapidly. Trying to enforce a fixed schema on this kind of data quickly becomes a limitation rather than a solution.&lt;/p&gt;

&lt;p&gt;This is where we realized that the choice of database would define the success of the entire system.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why MongoDB Atlas&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;We chose MongoDB Atlas because it allows data to be stored in a way that reflects its natural structure.&lt;/p&gt;

&lt;p&gt;Instead of forcing logs into predefined tables, MongoDB stores them as documents. This meant we could accept logs in any format and store them without restructuring or migration.&lt;/p&gt;

&lt;p&gt;This flexibility became essential as the system evolved.&lt;/p&gt;

&lt;p&gt;More importantly, MongoDB Atlas handled scaling without additional complexity. As the number of logs increased, the system continued to perform consistently, which is critical for real-time cybersecurity applications.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;MongoDB at the Core of the System&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;As development progressed, MongoDB Atlas became more than just a storage layer. It turned into the central point where all parts of the system connected.&lt;/p&gt;

&lt;p&gt;Every stage of ProShield-AI interacts with MongoDB:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Raw logs are stored&lt;/li&gt;
&lt;li&gt;Processed events are updated&lt;/li&gt;
&lt;li&gt;Incidents are tracked&lt;/li&gt;
&lt;li&gt;Attacker profiles are maintained&lt;/li&gt;
&lt;li&gt;Reports are generated&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;This made MongoDB not just a database, but the backbone of the entire platform.&lt;/p&gt;

&lt;p&gt;From Logs to Intelligence&lt;/p&gt;

&lt;p&gt;The system follows a simple but effective flow:&lt;/p&gt;

&lt;p&gt;Logs are collected, stored in MongoDB, processed using AI models, and then written back with additional insights.&lt;/p&gt;

&lt;p&gt;This continuous cycle allows the system to evolve with every new piece of data.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Log Ingestion and Storage&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The first step is collecting logs and storing them directly in MongoDB.&lt;/p&gt;

&lt;p&gt;Below is an example of how logs appear in the system:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F3llkz5a3mfip22kzfg3x.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F3llkz5a3mfip22kzfg3x.png" alt=" "&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fc7t1k7v4f8j11fymfwjv.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fc7t1k7v4f8j11fymfwjv.png" alt=" "&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;These logs are stored exactly as they are received, without enforcing structure. This ensures that no information is lost during ingestion.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Event Processing&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Once stored, logs are analyzed using a combination of anomaly detection techniques and rule-based logic.&lt;/p&gt;

&lt;p&gt;The system identifies unusual behavior, assigns risk scores, and classifies events based on severity.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Febtzrjzg7uasunds7sxv.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Febtzrjzg7uasunds7sxv.png" alt=" "&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fby0s9lid2aexc42jvexd.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fby0s9lid2aexc42jvexd.png" alt=" "&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;At this stage, raw logs are transformed into meaningful events that can be used for further analysis.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Building Incidents&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Individual events rarely tell the full story. Cyberattacks are sequences of actions.&lt;/p&gt;

&lt;p&gt;For example, a failed login attempt might be followed by privilege escalation and then data access.&lt;/p&gt;

&lt;p&gt;Instead of treating these separately, the system groups them into incidents.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fj8zaptrgvblxa7vmrx00.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fj8zaptrgvblxa7vmrx00.png" alt=" "&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;MongoDB makes this possible by allowing related data to be stored and queried together efficiently.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Attacker Intelligence&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;As more data is processed, patterns begin to emerge.&lt;/p&gt;

&lt;p&gt;The system builds attacker profiles based on behavior — such as repeated actions, attack styles, and progression patterns.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fvn62zdff0horui68kqtl.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fvn62zdff0horui68kqtl.png" alt=" "&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Since MongoDB does not enforce a rigid schema, these profiles can evolve naturally as new data is observed.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Predicting What Comes Next&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;One of the most impactful features of ProShield-AI is its ability to predict the next possible step in an attack.&lt;/p&gt;

&lt;p&gt;By analyzing previous patterns, the system can anticipate what an attacker might attempt next.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fa804o2j35yz1yrkgsnio.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fa804o2j35yz1yrkgsnio.png" alt=" "&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;This shifts the system from reactive to proactive, which is a key requirement in modern cybersecurity.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Reporting and Insights&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;At the final stage, all processed data is compiled into reports.&lt;/p&gt;

&lt;p&gt;These reports provide a clear summary of system activity, detected threats, and potential risks.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fls7id4vren5uj4nfhhxl.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fls7id4vren5uj4nfhhxl.png" alt=" "&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fq9zmeghsg5kbld2nbunt.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fq9zmeghsg5kbld2nbunt.png" alt=" "&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;MongoDB serves as the central repository for all this information, ensuring quick access and reliable storage.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What Made MongoDB Essential&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Looking back, several factors made MongoDB Atlas the right choice:&lt;/p&gt;

&lt;p&gt;It handled unpredictable data without requiring schema changes&lt;br&gt;
It scaled effortlessly with increasing log volume&lt;br&gt;
It supported fast read and write operations&lt;br&gt;
It integrated smoothly with AI-based processing&lt;/p&gt;

&lt;p&gt;Most importantly, it allowed us to focus on building the system, rather than managing the database.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Building ProShield-AI made one thing clear: in modern systems, the database is not just a storage component. It plays a central role in how data is processed, connected, and transformed into insights.&lt;/p&gt;

&lt;p&gt;MongoDB Atlas enabled us to work with real-world cybersecurity data in its natural form, without constraints.&lt;/p&gt;

&lt;p&gt;It allowed us to build a system that not only detects threats but also understands and predicts them.&lt;/p&gt;

&lt;p&gt;In that sense, MongoDB Atlas is not just supporting ProShield-AI — it is what makes the system possible.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Demo Video:&lt;/strong&gt;&lt;br&gt;
&lt;a href="https://youtu.be/zQQrSXcCysk?si=Q3DmLMt3PxlqqVEp" rel="noopener noreferrer"&gt;https://youtu.be/zQQrSXcCysk?si=Q3DmLMt3PxlqqVEp&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Github Repository:&lt;/strong&gt;&lt;br&gt;
&lt;a href="https://github.com/vishalreddy2006/Proshield-AI" rel="noopener noreferrer"&gt;https://github.com/vishalreddy2006/Proshield-AI&lt;/a&gt;&lt;/p&gt;

</description>
      <category>mongodb</category>
      <category>cybersecurity</category>
      <category>ai</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
