Plan on Sikkerhet.bouvet.no - For Security Champions in Bouvet

Roles and responsibilities

Mon, 01 Jan 0001 00:00:00 +0000

Bouvet conducts development projects in many different ways, where we take more or less responsibility for project management, planning, development, quality assurance, and not least the operation and management of the solution. We also involve our own, the client’s, and third-party equipment both during development and management of the solution.

Regardless of how the project is executed, it is important that we are aware of how responsibilities are divided. This should be regulated in the agreement with the client, so we must ensure that we:

Data and Classification

Mon, 01 Jan 0001 00:00:00 +0000

In short

Most organizations have different classification levels for both data and systems. The classification is often based on how data is used, where it is stored, and who can access it. This is a key requirement for any development project and must be clarified in advance.

Business Continuity

Mon, 01 Jan 0001 00:00:00 +0000

Business Continuity Planning is not an IT-technical subject. But it is our responsibility as suppliers of an IT system to remind the customer that the system can become unavailable. The answer from this planning will help describe the requirements for the solution’s robustness and security level, and is crucial for finding the right balance of cost and performance for the system.

Here it is important to consider

The criticality of the solution
Possible workarounds if the solution is unavailable
Consequences or extra work resulting from unavailability or when the solution becomes available again.

Customer Expectations

Do we have a Service Level Agreement with the customer that regulates uptime, availability, and similar, or does the customer have implicit expectations for this?

Using Artificial Intelligence

Mon, 01 Jan 0001 00:00:00 +0000

This page is about the use of AI in the development cycle, not the general use of AI solutions. The goal is to use AI as a productivity tool without losing control of security, quality, and traceability.

Want to learn more about AI?

Bouvet has its own portal for artificial intelligence at ai.bouvet.no, which helps you understand the technology and how it can be used in different roles. This article covers only the security side of the development cycle.

Security Checkpoints

Mon, 01 Jan 0001 00:00:00 +0000

Depending on the security level a delivery aims to achieve, it may be necessary to define mechanisms for assessing security at fixed points in the development cycle, known as security checkpoints.

These can be defined between logical phases in the project, for example, between the design and development phases, or when transitioning from development to the first release in production. Other and additional checkpoints can also be defined, entirely depending on the requirements the delivery team must adhere to.