Altinn / Altinn/altinn-studio-docs

Document security monitoring

Open
#1,630 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area/security
Dominant language
CSS
Stars
15
Forks
59
Avg merge
1d 11h
Merged PRs (30d)
53

Description

https://pedia.altinn.cloud/sec/security-architecture/security-operations/monitoring/ (or pages referred to from this page) should be updated with information on the SOC performs monitoring, and how the interfaces towards service owners and dev teams are.

Once approved, relevant parts should be migrated from pedia to docs.

Examples of questions the documentation should answer:

Hva slags sikkerhet har dere satt opp i Azure (nettverksovervåking etc)?
Hvordan vi kan/bør overvåke appene våre.
Hvilke verktøy finnes for å overvåke appene
Hva slags logg-nivå kan vi velge?
Hvordan setter vi opp varsling ved feil?
Hvilken overvåkning gjør Digdir av plattformen?
Hvilken overvåkning gjør Digdir av apper?
Hvilke alarmer gis for kjørende applikasjoner?
Hva får man av støtte til overvåkning, alarmer, logger etc?
Vil Digdir stille overvåkningsmuligheter som gjør det mulig å ivareta helsesjekker på TE egne tjenester? BR har blant annet et krav som viser til at det skal være mulig å varsle brukere om uventet nedetid så snart nedetid er kjent gjennom monitorering og kunne fange opp trender gjennom gode helsesjekker.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked Pedia security-monitoring page and the pages it refers to. Identify the SOC monitoring responsibilities, interfaces for service owners and development teams, and answers to the listed monitoring questions, then determine which approved sections should move to the Altinn Studio docs. Done means the monitoring documentation is updated and the approved relevant content is migrated.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
cloud, documentation, observability
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.