DevOps and Cybersecurity

		DevOps and Cybersecurity

DevOps and Cybersecurity
What is DevOps?
DevOps is the combination of cultural philosophies, practices, and tools that increases an organization's ability to deliver applications and services at high velocity: evolving and improving products at a faster pace than organizations using traditional software development and infrastructure management processes.

In a nutshell, DevOps is the teaming of infrastructure and development teams to speed the process of delivering applications and services for an institution.

What about teams or departments other than development?
The DevOps goal is to improve the communication and cooperation between the development and the infrastructure teams. Sadly, nothing is mention about the infrastructure needs for other departments' teams such as Sales, Marketing, Credit, Treasury, etc. These teams have web presence and run third party and customized software tools.

Our Intelligent Automated DevOps:
Our approach to DevOps is that DevOps is the foundation which everything hardware, software and virtual is created, monitored and maintained for the life of any system. Our analogy of our Intelligent automated DevOps is any running Operating System with all its services and protections. The functionalities of any Operating System are:

     1. Process management
     2. Files management
     3. Command Interpreter
     4. System calls
     5. Signals
     6. Network management
     7. Security management
     8. I/O device management
     9. ..etc

DevOps Support Diagram

Image #1

Image #1 presents a rough draft of the Continuous DevOps support and Intelligent Editors. The Continuous DevOps support is accessed by internet cloud, Business, Cybersecurity and users.

Note:
Our strategy of management and maintenance of any system is: first focusing on building Virtual-Automated-Tiers-Containers-Components DevOps. It would be the foundation for everything running on the system. With the success of building, testing and approving our DevOps. We would be able to clone or build reusable templates for other projects. The return on the investment (ROI) would be worth such effort.

Our DevOps is composed of the following Virtual-Automated-Tiers-Containers-Components:

1. Central Intelligent Management (DevOps Kernal) Our Structure and Management: The main goal of Central Intelligent Management (DevOps Kernal) is build a solid structure with intelligent components which can be easy integrated into other system. Managing these intelligent components would be done both with automation of management processes and procedures plus using human intelligent management teams to run and manage any platform as well as the interfaces. See our site: SamEldin.com with our Intelligent Management approaches using matrices.
2. Machine Learning tools and services See our site: SamEldin.com for our ML approaches and tools. ML Management Engines - Control: Management is the core of any system and our ML is no exception, the management Control is also composed of Engines and a Leading Control Engine.
3. Intelligent Editors What is Our Intelligent DevOps Editor(s)? How can we build such an Intelligent DevOps Editor? The key feature of our DevOps Editor is Intelligence. Intelligence here is not Artificial Intelligence, but developing intelligence software. We communicate with gurus of development and infrastructure, and try to pick their brains. We build a number of processes and tasks mimicking these gurus handling and approaches. We rearrange these processes and tasks in order to be able to translated them to code and a running software. With the computer processing speed, thousands if not hundreds of thousands of processes and options can be performed on the input data in seconds. These processes add to intelligence of our editor. DevOps Editor GUI Interface To make our Intelligent DevOps Editor concept easier to understand, we may need to present a picture. We are presenting a markup or a running prototype with a GUI interface for our audience to examine. Our Intelligent DevOps Editors We have architected-designed and created prototypes for six DevOps Editors. We recommend that our viewers visit the following links and checkout each editor. We are open for feedbacks and comments ( Sam@SamEldin.com ): Data Center Specification Editor Data Center Specification Network Editor Data Center Specification Migration Editor Data Center Migration Builder Data Center's Testing - Tracking - Validation Editor Intelligent DevOps Editor - "Turn Key"
4. Manual Monitoring We need to develop GUI interfaces for manual tools to manually monitor any running system. Human intelligence and experience are needed.
5. Cloning Services Rollback, backups, tracking history or creating system on run can use cloning for faster processes.
6. Reusable Templets (Platforms, Networks, frameworks, storage) Reusable of templates, cloning and code are great tools for faster processes.
7. Drivers The use vendors’ driver as well as homemade drives are helpful in reusability and automation.
8. Automated intelligent Services Scripts Automation and templates building would require customized and all purposes scripts. Most of our automation would be built from usable scripts.
9. Reverse Engineering Services Vendors and homemade reverse engineering tools are part of our services for cybersecurity.
10. OS Monitoring 11. Processes Monitoring 12. Storage Monitoring 13. Tracking 14. Cybersecurity Management – setup, scanning, detection, prevention, remedy Our Case Study - Autonomous Vehicles https://sameldin.com/CaseStudiesFolder/CaseStudies_AutonomousVehicles.html Our Case Study - Autonomous Vehicles page presents our architected, design and some Java code which addresses Cybersecurity monitoring including OS, processes, storage, tracking and Management – setup, scanning, detection, prevention and remedy. We create one webpage to present: Scanning, Tracking, Detecting and Remedy All the Internal Software and the Hardware The following link has one segment of our Case Study - Autonomous Vehicles presentation of: One Segment of Our Case Study - Autonomous Vehicles
15. Software Services – Third party software, development Software, third party software, development, or anything running on the VMs must be tracked and monitored with a timestamp. Audit trial of all software and hardware must be performed plus their history must be saved to NAS.
16. IP and VIP Management IP and VIP Management is critical to Cybersecurity and tracking of clients, hackers, users, remote access, interfaces and even internal system. Internal VIP can be created to track internal users and the VMs created for them.
17. Rollback Services VMs for Rollback servers would be created with every production VM. Updating Rollback VM must be done on a regular basis or scheduled pattern.
18. Backup Backup to NAS, filing system, databases or form of storage must be done early and done often. ML would be accessing these backup systems.
19. Batch Batch processes must be also tracked and audit trailed and added to ML and history.
20. Testing Everything running on our DevOps must be virtual tested and specially updates and third parties' software.
21. System Evaluation Must be automated and scheduled with dynamic parameters. For example, VMs created for certain clients and our system often detect malicious code and other hacking attacks, then all IP, VIP, routing, detection, remedy, backup, … must be evaluated to see what and how can we improve handling these clients and our recommendation to help with hacking. In short, our system and our clients, vendors, users, employees, management interfaces and usage must be evaluated. Virtual Intelligent Automated evaluation processes must be developed with ML support and history.
22. Lessons Learned Lessons learned from past projects are tools you can use as a project manager to drive improvement within your team. We’ve compiled expert advice on how to collect, document, and apply lessons learned toward future endeavors. Create Lessons Learned Templates.
23. Training Ongoing and web-mobile based.