Segurity Events

Web application for managing and tracking security incidents, events, evidence, and indicators. Prototype developed for the Alcaldía de Medellín, 2021.

Author: Carmen Juliana Ibáñez Grajales — I.U. Pascual Bravo

---

Tech Stack

Layer	Technology
Backend	C# / ASP.NET Web Forms / .NET Framework 4.8
Database	SQL Server (ADO.NET + Stored Procedures)
Frontend	Bootstrap 5.0.0-beta3 · jQuery 3.6.0 · Font Awesome 5.15.3
Export	NPOI 2.5.3 (.xlsx files)

---

Prerequisites

• Visual Studio 2019 or later
• .NET Framework 4.8
• SQL Server (any edition supporting T-SQL)
• IIS Express (included with Visual Studio)

---

Setup

1. Database

Run the following scripts against your SQL Server instance in order:

1. Segurity_Events_Web/Scripts/Base de datos.sql — creates the Segurity_Events_DB database and all tables.
2. Segurity_Events_Web/Scripts/Procedimientos_Almacenados.sql — creates all stored procedures.

2. Connection string

Update the connection string in two places to point to your SQL Server instance:

Segurity_Events_Web/Web.config

<add name="Segurity_Events_DBConnectionString"
     connectionString="Data Source=<SERVER>;Initial Catalog=Segurity_Events_DB;Integrated Security=True"
     providerName="System.Data.SqlClient"/>

Segurity_Events_Web/Conexion.cs

public static string cadena = "server=<SERVER>; database=Segurity_Events_DB; integrated security=true";

---

Running in development

1. Open Segurity_Events.sln in Visual Studio.
2. Press F5 to build and launch with IIS Express.
3. The application will be available at https://localhost:44323.
4. Entry point: Inicio.aspx (login/welcome page).

Command-line build:

msbuild Segurity_Events.sln /p:Configuration=Debug /p:Platform=AnyCPU

---

Modules

Module	Page	Description
Home	Inicio.aspx	Login / welcome screen
Incidents	Incidentes.aspx	Incident CRUD, search, and Excel export
Events	Eventos.aspx	Associated event logging
Evidence	Evidencia.aspx	Supporting document management
Categories	Categoria.aspx	Incident classification taxonomy
Indicators	Indicadores.aspx	Security KPIs / metrics
Historical	Historico.aspx	Historical data view
Downloads	Descargas.aspx	Bulk data export
Search Incidents	Buscar_Incidentes.aspx	Incident search and filtering
Search Categories	Buscar_Categoria.aspx	Category search

---

Architecture

The project follows a 3-tier pattern without a dedicated business logic layer — code-behind files (*.aspx.cs) hold validation logic and make direct ADO.NET calls to SQL Server stored procedures.

*.aspx  (ASP.NET server controls)
  └── *.aspx.cs  (code-behind: validation + SQL calls)
        └── Conexion.cs  (connection string)
              └── SQL Server: Segurity_Events_DB
                    └── Stored Procedures (SP_Insert_*, SP_Select_*, SP_Delect_*)

Excel export is handled by the NPOI library via DataTableToExcel() helper methods defined in each code-behind that requires it.

---

Documentation

File	Description
Segurity_Events_Web/Docs/Manual de uso Segurity Events.docx	End-user manual
Segurity_Events_Web/Docs/Requerimientos Segurity Events.docx	System requirements
Segurity_Events_Web/Docs/Modelado de Datos Segurity Events.PNG	Data model diagram
Segurity_Events_Web/Docs/Entrega Informe Final.pdf	Final delivery report
Segurity_Events_Web/Docs/Componentes usados en el ambiente de desarrollo.docx	Dev environment components

---

Production deployment

1. Update the connection strings (see Setup section above).
2. Publish via Visual Studio (Build → Publish) or MSBuild in Release mode:

   msbuild Segurity_Events.sln /p:Configuration=Release /p:Platform=AnyCPU

3. Deploy the published files to an IIS site with .NET Framework 4.8 installed.
4. Ensure the application pool identity has access to the configured SQL Server instance.