MAINSYSTEMS 
identify confidentiality defects before using real data
1. Regulatory Concept & Core Standards
In this video we will consolidate a skill: identify confidentiality defects before using real data. Use the case to test what you would do in a similar situation. We will explain the proposed response step by step so that you can understand each choice and recognise when more information would be needed. Implementation combines legal assessment and actual working arrangements. Technology alone does not provide independence, responses and protection. Platform examples are testing methods; verify each real UNOVOX configuration in its own environment.
Tests cover receipt, dialogue, rights and timing. Identity can escape through an email subject or screen notification. Section 11 and security requirements concern all processing. A launch date does not justify ignoring a known defect.
Apply the following rule: Section 7(2) requires acknowledgement and a preliminary recognition decision promptly and no later than seven days after receipt. Notify the decision within three days after making it. Provide progress information within two months after recognition as a whistleblower report and outcome information after examination. Private entities apply section 7 paragraphs 2,5,7 and 8; public-body exceptions must not automatically be imported.
2. Practical Implementation & Procedure
Use an authorised test environment and fictional data. Check blocked access, message contents and cover. Assign correction and retest. Base launch on results and assessed limits. Before moving on, turn this procedure into a sequence you could explain to a colleague. Identify the first check, the action that depends on its outcome and the record that allows the decision to be reconstructed. Follow the sequence on screen and identify the point where an error would change the result.
3. Case Study & Compliance Action
A test email subject names the reporter and appears on a shared screen. The team replaces it with a neutral reference and tests authorised secure access. Now read the case carefully. Separate established facts from information you would still need to confirm. Do not add motives or events that have not been described. This distinction matters when choosing a response proportionate to the information available.
The exercise is as follows: Does an announced launch date justify a confidentiality defect? Choose an answer and write one sentence explaining it. During the pause, compare your choice with the criteria we have just considered. Also think about the material you would retain to explain the decision later.
No. Correct it and verify the result. A date does not remove protection requirements; only then can use be assessed properly.
One mistake to avoid is: subordinating security to the campaign schedule.
Now apply the national rule to a second decision. The platform counts 90 days from opening. Does this meet Latvian requirements?
No. Separately record receipt, recognition decision and notification. Acknowledgement and initial decision are due within seven days after receipt; notify the decision within three days after making it. Progress information is due within two months after recognition. Apply section 7(1)’s distinction between public and private organisations.