Data security and data leakage protocol
Why we train our team in security awareness and how we handle incidents
For the organizations we work with, security is not a background topic. It is a hard precondition for collaboration.
In projects with sensitive data, multiple stakeholders and complex processes, one question is leading:
can you trust everyone to handle information carefully?
For our clients, this is not a detail. It is the bottom line.
That’s why we train our team in security awareness. And that’s why we have our processes in place in case something does go wrong.
Connecting to a high level of requirements
Our clients work in environments with clear and often strict security policies. This applies to accessing systems, sharing documents and the way information is managed.
This is reflected in the nature of the organizations we work with, and in the demands they place on their partners. Anyone who wants to operate in that environment must demonstrably function at the same level.
Security awareness training is a first step in this.
Not as an obligation, but as part of professional conduct.
Security is in behavior
Most risks arise not from systems but from everyday actions.
Opening an e-mail.
Sharing a document.
Responding to a request.
By training our team, we ensure that these moments become conscious. That everyone recognizes when something deviates and knows what to do.
This leads to consistent behavior, less uncertainty and more control in the process.
What happens if something does go wrong
No matter how well you design your processes, risks never completely disappear. Therefore, it is essential that you not only prevent, but also be prepared.
Within NewArmstrong, we work with an established protocol for security incidents in Data leak response plan.
This protocol describes how we handle situations such as phishing, account compromises, malware and possible data breaches. The aim is to limit damage, ensure continuity and inform clients correctly and in a timely manner.
This is not just about technology, but above all about structure and responsibility.
A clear and controlled process
When an incident occurs, we work according to a set process that is initiated immediately.
First, the incident is reported and recorded. This is followed by an analysis in which the nature and impact are determined. Based on this, we take immediate measures to prevent further damage, for example by blocking accounts or isolating systems. Systems are then restored and additional monitoring is applied.
This is followed by communication to the parties involved and a determination of whether there are obligations under laws and regulations, such as the AVG. Finally, the incident is evaluated and structural improvements are recorded.
This ensures an approach that is not ad hoc, but controlled and demonstrable.
Clear roles and responsibilities
An important part of the protocol is to establish in advance who does what.
There is always a person responsible for coordination and decision-making. Technical analysis and remediation lie with a security lead. There is also a role for privacy and legal assessment. Communication to clients is deliberately organized through a single point of contact (account lead).
This prevents noise and ensures quick and unified action.
Transparency towards clients
In a situation where something goes wrong, communication is at least as important as the solution itself.
Therefore, the protocol defines how and when principals are informed. Communication is factual, timely and proportionate. At a minimum, this involves sharing what has happened, what the impact is, what measures have been taken and what any follow-up steps are.
For clients, this means not depending on assumptions, but having insight into what is happening.
Connecting to different customer environments
Not every client demands the same thing. Therefore, we take into account differences in requirements and context.
Some organizations require immediate escalation and full audit trails. Other situations place more emphasis on continuity or confidentiality of specific data. The protocol addresses this by providing an appropriate course of action for each type of client and risk.
This ensures that our way of working is not generic, but tailored to the environment in which we operate.
Part of how we work
Security awareness training and the incident protocol are not separate. Together, they form one whole. The training ensures that risks are recognized earlier.
The protocol ensures structured action when needed.
Both contribute to the same goal: maintaining control of the process.
We train our team because our clients work in an environment where mistakes can have major consequences.
And we set up our processes because we know that security is not only in prevention, but also in how you act when necessary.
This leads to better behavior, clear processes and transparency towards clients.
And ultimately to what matters most to these projects:
certainty in every step of the process.
Want your design to go skyhigh? Let's talk!
Marie Antoinette Freeblood
Operational manager Design
Leidsevaartweg 1
2106 NA Heemstede
+31 88 007 2600
