Operations and Maintenance Flashcards
Operations security
staying secure or keeping the resiliency levels of the software above the acceptable risk levels.
The different types of operations security controls are
Detective; Preventive; Deterrent; Corrective; Compensating.
Detective Controls
are those that can be used to build historical evidence of user and system/process actions. E.g. auditing (logging), intrusion detection systems (IDS).
Preventive Controls
are those which make the success of the attacker difficult as its goal is to prevent the attack actively or proactively. E.g. Input validation, output encoding, bounds checking, patching, intrusion prevention systems (IPS).
Deterrent Controls
are those, which don’t necessarily prevent an attack nor are they merely passive in nature. Their aim is to dissuade an attacker from continuing their attack. E.g. auditing when the users of the software are aware of being audited,
Corrective Controls
are those which aim to provide the recoverability of software assurance. E.g. Load balancing, clustering, failover of data and systems.
Compensating Controls
are those controls that must be implemented when the prescribed software controls as mandated by a security policy or requirement cannot be met due to legitimate technical or documented business constraints. E.g.
Ongoing activities that are useful to ensure that the
software stays secure:
Monitoring; Incident Management; Problem Management; Change Management including Patch and Vulnerability Management; Backup, Recovery and Archiving.
Monitoring can be used to:
Validate compliance to regulations and other governance requirements; Demonstrate due diligence and due care on the part of the organization towards its stakeholders; Provide evidence for audit defense; Assist in forensics investigations; Identify new threats; …
What to monitor
Any operations that can have a negative impact on the brand and reputation of the organization, when it does not function as expected, must be monitored.
The PCI DSS as one of its requirements mandates that
Any physical access to cardholder data or systems that house cardholder data must be appropriately restricted and the restrictions periodically verified.
The primary ways in which monitoring is accomplished within organizations today is by
Scanning; Logging; Intrusion detection.
Audits are monitoring mechanisms by
which an organization can attest the assurance aspects (reliability, resiliency and recoverability) of the network, systems and software that they have built or bought.
They are effective to determine the implementation and effectiveness of security principles such as
Separation of duties and least privilege.
Some of the reasons as to what periodic audits of software can be used for
Determine that the security policy of the software is met; Assure data confidentiality, integrity and availability protections; Make sure that authentication cannot be bypassed; Ensure that rights and privileges are working as expected; Check for the proper function of auditing (logging); Check for the proper function of auditing (logging); Find out if the unnecessary services, ports, protocols and services
are disabled or removed; …
Incident management activities
The proper protocols to follow and the steps to take when a security breach (or incident) occurs.
NIST Special Publication on Computer Security
Incident Handling Guide (SP 800-61)
guidance on how to manage computer security incidents effectively.
NIST Special Publication SP 800-61
NITS SP 800-61 (Computer Security Incident Handling Guide) guidance on how to manage computer security incidents effectively.
The first step in incident response is to determine
If the reported or suspected incident is truly an incident or not. If it is a valid incident, then the type of the incident is determined.
Incident management shall define clear procedures to
to assess the current and potential business impact and risk must be established along with the implementation of effective and efficient mechanisms to collect, analyze and report incident data.
Event
Any action that is directed at an object which attempts to change the state of the object.
Red flags
It is generated when events match preset conditions or patterns upon further analysis. E.g. adverse events include flooded networks, rootkit installations, unauthorized data access, malicious code executions or business disruptions.
Alerts
flagged events that need to be scrutinized further to determine if the event occurrence is an incident. Alerts can be categorized into incidents.
Security incidents
Adverse events that violate or threaten to violate the security policy of the network, system or software
applications.
Types of Incidents
Denial of Service (DoS); Malicious Code; Unauthorized Access; Inappropriate Usage; Multiple Component.
Incident Response Process
Preparation, detection and analysis, containment, eradication and recovery, and post-incident analysis.