Software Security Development CYB0203 Lecture Notes PDF

AL- Imam Muhammad Bin Saud Islamic University. Computer Science (Cyber Security). Applied College. Ministry of Education. Sau...

AL- Imam Muhammad Bin Saud Islamic University. Computer Science (Cyber Security). Applied College. Ministry of Education. Saudi Arabia. Software Security Development CYB0203 Edited by: Ashwag Gashgari. Chapter1: Introduction, Why Design Matters For Security Chapter 2: Domain Driven Design  Outline Why Design Matters for Security. What Are the Benefits of Security by Design? Reasons why an effective web application is necessary. The Practices to create a well secured system. Domain-Driven Design. Example of Domain-Driven Design. Advantages of Domain-Driven Design. Disadvantages of Domain-Driven Design.  Why Design Matters for Security. In the context of cybersecurity, "design" refers to the intentional and systematic process of planning, organizing, and implementing the structure and components of a system or application with a primary focus on ensuring security. This encompasses various aspects beyond mere aesthetics, emphasizing the development of systems that are resilient to potential threats, robust against vulnerabilities, and capable of protecting sensitive information.  Why Design Matters for Security. Security design involves strategic decision-making to create a framework that not only addresses current security concerns but also anticipates and mitigates potential risks in the future. It includes considerations such as access controls, encryption, authentication mechanisms, secure coding practices, and the overall architecture of the system. It takes a security-first approach in web development by identifying and implementing the security requirements of your design at every stage of development.  What Are the Benefits of Security by Design? 1. Preventing Vulnerabilities: 1. Thoughtful Architecture: Well-designed systems incorporate security considerations into their architecture from the start. This includes identifying potential vulnerabilities and implementing safeguards to mitigate risks. 2. Secure Coding Practices: A design focused on security encourages the use of secure coding practices. This reduces the likelihood of common vulnerabilities such as injection attacks, buffer overflows, and other coding errors.  What Are the Benefits of Security by Design? 2. User-Friendly Security Measures: 1. Balancing Usability and Security: Effective security design strikes a balance between robust security measures and user-friendliness. Users are more likely to adhere to security protocols and guidelines when they are seamlessly integrated into the design. 2. User Education: Design can facilitate user education by presenting security information in a clear and understandable manner, reducing the chance of human errors that could compromise security.  What Are the Benefits of Security by Design? 3. Early Detection and Mitigation: 1. Threat Modeling: Designing with security in mind involves the early identification of potential threats through techniques like threat modeling. This allows for proactive measures to be taken to address vulnerabilities before they can be exploited. 2. Secure Development Lifecycle: Integrating security into the software development lifecycle from the design phase ensures that security measures are consistently applied, reducing the likelihood of overlooking critical aspects.  What Are the Benefits of Security by Design? 4. Resilience Against Evolving Threats: 1. Adaptive Design: Systems designed with security in mind are more adaptable to emerging threats. Such designs are capable of evolving to counter new and sophisticated attack vectors. 2. Security Updates and Patching: A well-designed system includes mechanisms for regular updates and patching to address vulnerabilities promptly, helping to maintain a robust security posture over time.  What Are the Benefits of Security by Design? 5. Visual Deterrents and Cues: 1. Security Indicators: Design can incorporate visual elements such as warning signs, indicators, and logos that convey the presence of security measures. These visual cues act as deterrents to potential attackers. 2. User Feedback: Providing immediate and clear feedback to users about security-related actions, successes, or issues enhances their understanding and compliance with security protocols.  What Are the Benefits of Security by Design? 6. Inclusive Security: 1. Accessibility: A secure design is inclusive, considering the needs of diverse user groups, including those with disabilities. This ensures that security measures are accessible to all users. 2. Cultural Sensitivity: Designing security measures with cultural sensitivity in mind promotes adherence to security practices across different user demographics. 7. Cost-Effective Security: 3. Security by Design: Incorporating security from the beginning of the design process is more cost-effective than trying to retrofit security measures into an existing system. It minimizes the risk of costly security breaches and the subsequent need for extensive remediation. Reasons why an effective web application is necessary Sensitive Data Revenue Regulatory Compliance  The Practices to create a well secured system Conduct Regular Security Audits Adopt Real-Time Security Monitoring Encrypt Your Data Uphold Standard Login Practices Cultivate Strong Password Culture Provide Web Application Security Training  Domain-Driven Design Domain-driven design (DDD): is a major software design approach, focusing on modeling software to match a domain according to input from that domain's experts.  Domain-Driven Design Domain: It refers to the subject area or problem space that the software system is being built to address. It encompasses the real-world concepts, rules, and processes that the software is intended to model or support. For example, in a banking application, the domain includes concepts like accounts, transactions, customers, and regulations related to banking operations.  Domain-Driven Design DDD introduces the concepts of strategic design, focusing on high-level organizational patterns, and tactical design, which involves making specific design decisions at the code level. These two aspects work together to align the software design with the business domain.  Domain-Driven Design 1. Strategic Design: 1. Purpose: Strategic design addresses high-level organizational and architectural concerns, aiming to align the entire development effort with the business goals and domain requirements. 2. Key Elements: 1. Bounded Contexts: Identifying and defining the boundaries of different contexts within the system, where a specific model or concept has a distinct meaning. 2. Context Mapping: Managing interactions and integration points between different Bounded Contexts, acknowledging the relationships and boundaries between them. 3. Shared Kernel: Establishing a common ground or shared subset of the domain model that is collaboratively developed and agreed upon by multiple Bounded Contexts. 4. Anti-Corruption Layer (ACL): Implementing a translation layer between different Bounded Contexts to prevent the corruption of models and data as they interact. 5. Ubiquitous Language refers to a shared vocabulary or language that is used consistently and universally across all stakeholders involved in the development of a software system. This language consists of terms, phrases, and concepts that accurately represent domain knowledge and concepts.  Domain-Driven Design 2. Tactical Design: 1. Purpose: Tactical design involves making specific design decisions at the code level, focusing on the implementation details of individual components and entities. 2. Key Elements: 1.Entities and Value Objects: Defining and modeling the core building blocks of the domain, such as entities with distinct identities and lifecycles, and value objects that are immutable. 2.Aggregates: Grouping entities and value objects into aggregates to manage transactional consistency and encapsulation. 3.Repositories: Handling the retrieval and persistence of aggregates, abstracting away the data access layer. 4.Domain Services: Implementing domain-specific operations or processes that don't naturally belong to a specific entity. 5.Domain Events: Capturing and handling significant changes in the state of the system to communicate and react to domain-specific occurrences.  Example of Domain-Driven Design Lets say, we are developing a ride-hailing application called “RideX.” The system allows users to request rides, drivers to accept ride requests, and facilitates the coordination of rides between users and drivers. How to apply the domain driven design on the previous example? Ubiquitous Language 1. User: Refers to individuals who request rides via the RideX platform. 2. Driver: Refers to individuals who provide rides to users via the RideX platform. 3. Ride Request: Represents a user’s request for a ride, specifying details such as pickup location, destination, and ride preferences. 4. Ride: Represents a single instance of a ride, including details such as pickup and drop-off locations, fare, and duration. 5. Ride Status: Represents the current status of a ride, such as “Requested,” “Accepted,” “In Progress,” or “Completed.”  Example of Domain-Driven Design Bounded Contexts 1. Ride Management Context: Responsible for managing the lifecycle of rides, including ride requests, ride assignments to drivers, and ride status updates. 2. User Management Context: Handles user authentication, registration, and user-specific features such as ride history and payment methods. 3. Driver Management Context: Manages driver authentication, registration, availability status, and driver-specific features such as earnings and ratings.  Example of Domain-Driven Design Entities and Value Objects 1. User Entity: Represents a registered user of the RideX platform, with properties like user ID, email, password, and payment information. 2. Driver Entity: Represents a registered driver on the RideX platform, with properties like driver ID, vehicle details, and driver status. 3. Ride Request Entity: Represents a user’s request for a ride, including properties like request ID, pickup location, destination, and ride preferences. 4. Ride Entity: Represents a single instance of a ride, including properties like ride ID, pickup and drop-off locations, fare, and ride status. 5. Location Value Object: Represents a geographical location, with properties like latitude and longitude.  Example of Domain-Driven Design Ride Aggregate: Consists of the Ride Entity as the aggregate root, along with related entities such as Ride Request, User, and Driver entities. The Ride Aggregate encapsulates the logic for managing the lifecycle of a ride, including handling ride requests, assigning drivers, and updating ride status. Ride Repository: Provides methods for querying and storing ride-related entities, such as retrieving ride details, updating ride status, and storing ride-related data in the database. Ride Assignment Service: Responsible for assigning available drivers to ride requests based on factors such as driver availability, proximity to pickup location, and user preferences. Payment Service: Handles payment processing for completed rides, calculating fares, processing payments, and updating user and driver payment information. Domain Events RideRequestedEvent: Represents an event triggered when a user requests a ride, containing information such as the ride request details and user ID. RideAcceptedEvent: Represents an event triggered when a driver accepts a ride request, containing information such as the ride ID, driver ID, and pickup location.  Advantages of Domain-Driven Design Shared Understanding. Alignment with Business Goals. Improved Collaboration. Modularity and Flexibility. Scalability. Better Risk Management. Adaptability to Change.  Disadvantages of Domain- Driven Design Deep domain knowledge is needed. Contains repetitive practices. It encourages the use of continuous integration to build strong applications that can adapt themselves when necessary. It might not work best for highly-technical projects. Domain-driven design is perfect for applications that have complex business logic.  End. Thank you. Any Questions?