Type of work 03 of 04

Cybersecurity

Code review

Reading the source code, within the scope set out in the quote, to find its security weaknesses and the places where a fix is worth the most.

Builds onDigital security

Two students reviewing code on a laptop, a notebook covered in notes beside it
Fig. 1Reviewing code in pairs.

Definition

What it is

A code review examines the program itself, not only how it behaves: how it checks what it receives, how it handles secrets, how it controls access, how it deals with errors, and which libraries it uses and in which versions. It assumes access to the repository, within a scope agreed in advance.

Our work

What we do

The team reads the code within the scope set out in the quote, then writes an audit report: each finding is located in the code, explained, and comes with recommendations ranked by priority.

During the free scoping call, we define with you the repository, the parts of the code to review and the access needed.

Deliverable

What you receive

The deliverable is defined in the quote. You receive it at the close-out step, and a handover session then closes the project.

What you receive at the end of the project, and at which step
DeliverableContentsHanded over at
DeliverableAudit reportContentsThe findings located in the code and prioritised recommendations, within the scope set out in the quote.Handed over at05 · Close-out and support
DeliverableHandover sessionContentsA session to hand over the deliverable, walk you through how it works and its documentation, and answer your questions.Handed over at05 · Close-out and support

Next step

Let’s talk about your project. The scoping call is free.

An initial conversation to understand your need, then a written quote: scope, deliverables, timeline, price.

Email the board

junior.eurecom.tech@gmail.com

  1. 01You describe what you need.
  2. 02We scope the project with you.
  3. 03You receive a written quote.