How bcicdis/security works
Project type and purpose
• From the README (“System Security Monitoring”) and file tree, this is an open‐source security tool comprising:
• A system monitoring daemon written in Ada (src/monitor_daemon.adb, default.gpr, obj/)
• A stand-alone Python “military_grade_encryption” module for encrypting/decrypting data (cryptography/military_grade_encryption/)
• Purpose: continuously collect system events/logs, provide military‐grade encryption utilities to secure those logs or other files.
File structure
• Top‐level:
• src/ & obj/ → Ada sources, compiled artifacts, logs, GNAT project file
• cryptography/military_grade_encryption/ → Python CLI tools (encrypt.py, decrypt.py), package (encryptor/) and sample data
• default.gpr → Ada build configuration
• Patterns:
• Separate language boundaries (Ada vs. Python)
• CLI + library structure in Python (encryptor package under utils & aes_encryptor)
• Build artifacts isolated under obj/
a. Main components
1. Monitor Daemon (Ada)
– Source: src/monitor_daemon.adb
– Build: default.gpr → obj/monitor_daemon.exe
– Output: system event logs (obj/monitor_log.txt)
2. Encryption CLI (Python)
– encrypt.py / decrypt.py
– Uses encryptor library: aes_encryptor.py + utils.py
3. AES Encryptor Library (Python package)
4. Data Store / Filesystem
– Plain logs, sample.txt, encrypted files (.enc)
5. (Optional) External Systems / Admin Console
– Operators invoke Python scripts on the logs or feed files to the daemon.
b. Relationships & data flow
– Monitor Daemon → writes plain-text logs → Data Store
– Operator/Admin → runs encrypt.py against logs → calls AES Encryptor Library → produces encrypted .enc files → back to Data Store
– decrypt.py reverses the flow for analysis
– (Future) Daemon could call encryption library directly via subprocess or API
c. Architectural patterns & principles
– Separation of concerns:
• Monitoring (Ada)
• Encryption (Python CLI + library)
– Layered approach: CLI layer atop a reusable library layer
– Clear build vs. runtime separation (obj/ vs. src/cryptography)
– Single Responsibility Principle: each component focuses on one aspect
d. Key technologies & frameworks
– Ada / GNAT (default.gpr) for high-integrity daemon
– Python 3.x for encryption utilities
– AES algorithm (in aes_encryptor.py)
– Standard filesystem as data store