Security training for the development team should begin in the initiation phase of the System Development Life Cycle (SDLC). This is the phase where the security requirements and objectives are defined and the project scope and feasibility are determined. The development team should be aware of the security expectations and best practices from the start of the project, and receive continuous training throughout the SDLC. The other phases are not the best time to start security training, as they involve more specific tasks such as design, coding, testing, deployment, and maintenance.

Session continuity is the ability to maintain a connection between a client and a server without interruption or loss of data. When deploying an IDS on a high-volume network, the need to distribute the load across multiple sensors would create a technical problem of session continuity, as the sensors may not be able to track the state of the sessions and correlate the packets from different sources. This could result in false positives or false negatives, or degrade the performance of the IDS.

A logic bomb is a piece of code that is inserted into software to trigger a malicious function when a certain condition is met, such as a specific date, time, or event. A logic bomb can cause various types of damage, such as deleting or encrypting data, crashing the system, or launching other attacks. A logic bomb is often hidden or disguised within legitimate software, making it difficult to detect or prevent. A logic bomb is different from phishing, salami, or back door attacks, which are defined as follows:
Phishing is a type of social engineering attack that uses fraudulent emails or websites to trick users into revealing their personal or financial information, or installing malware on their devices.
Salami is a type of fraud that involves stealing small amounts of money or data from multiple sources over time, hoping that the theft will go unnoticed or be ignored.
Back door is a type of covert access that bypasses the normal authentication or authorization mechanisms of a system or network, allowing unauthorized users or attackers to gain access or control.

A data retention policy is a document that specifies the rules and guidelines for how long and under what conditions an organization should retain its data. The main goal of a data retention policy is to ensure the integrity and confidentiality of data for a predetermined amount of time.
Integrity means that the data is accurate, complete, and consistent, and that it has not been modified or corrupted by unauthorized parties. Confidentiality means that the data is protected from unauthorized access or disclosure, and that it respects the privacy and security of the data owners or subjects. A data retention policy can help an organization to comply with the legal or regulatory requirements, to support the business or operational needs, and to reduce the storage or management costs of the data. Ensuring that data is destroyed properly, ensuring that data recovery can be done on the data, and ensuring the availability of data for a predetermined amount of time are not the main goals of a data retention policy, as they are related to the disposal, restoration, or accessibility of the data, not the integrity or confidentiality of the data.