Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Functional Design: E-mail report #334

Open
1 of 7 tasks
TwistMeister opened this issue Jan 12, 2023 · 1 comment
Open
1 of 7 tasks

Functional Design: E-mail report #334

TwistMeister opened this issue Jan 12, 2023 · 1 comment
Assignees
@stephanie0x00 @HeleenSG
Labels
design keiko Issues related to keiko report rocky Issues related to Rocky

Comments

@TwistMeister
Copy link
Contributor

TwistMeister commented Jan 12, 2023 •
edited
Loading

  • Think about and document the desired flow te create a report : look at the designs that were made earlier
  • Find out what a user wants to find in this report?
  • -- Overview of E-mail related DNS-records and their configs
  • -- Mailserver status
  • -- "Rijkseisen"?
  • Content proposal (wireframes)
  • Review with Noemi (optional?)
@TwistMeister TwistMeister self-assigned this Jan 12, 2023
@TwistMeister TwistMeister changed the title Functional Design: E-mail report [OpenKAT v1.6] Functional Design: E-mail report Jan 16, 2023
@TwistMeister TwistMeister changed the title [OpenKAT v1.6] Functional Design: E-mail report [OpenKAT v1.7] Functional Design: E-mail report Jan 30, 2023
@dekkers dekkers transferred this issue from minvws/nl-kat-rocky Feb 28, 2023
@dekkers dekkers added the rocky Issues related to Rocky label Feb 28, 2023
@TwistMeister TwistMeister changed the title [OpenKAT v1.7] Functional Design: E-mail report Functional Design: E-mail report Mar 1, 2023
@Rieven Rieven added the keiko Issues related to keiko label Aug 17, 2023
@NoemiOverdijk NoemiOverdijk mentioned this issue Sep 5, 2023
Open
@underdarknl underdarknl added this to the OpenKAT v1.15 milestone Dec 22, 2023
@stephanie0x00
Copy link
Contributor

I think the following components should definitely be in this report:

Email report:

  • Open ports (IMAP, SMTP, POP3)
  • TLS/SSL config of the services (to check if the server supports secure ciphers)
  • MX records
  • IPv4/IPv6 connectivity (mandatory for e-mail by Forum Standaardisatie for the Dutch government)
  • STARTTLS/DANE/DMARC/DKIM/SPF (mandatory for e-mail by Forum Standaardisatie for the Dutch government)
  • IMAP/SMTP are recommended by Forum Standaardisatie. These are government specific checks, for other environments the use of POP3 (below) could be acceptable. Thus some kind of selection criteria for the organisation could be used, eg. on the organisation page you specify your country and organisation type maybe. If available configs are present, these could be applied.
  • POP3 is archived and should not be used based on the recommendation from Forum Standaardisatie
  • Have I been pwned overview?

@NoemiOverdijk NoemiOverdijk removed this from the OpenKAT v1.15 milestone Apr 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@stephanie0x00 stephanie0x00

@HeleenSG HeleenSG

Labels
design keiko Issues related to keiko report rocky Issues related to Rocky
Projects
KAT
Status: No status
KAT - Reports
Status: No status
Milestone
No milestone
Development

No branches or pull requests
7 participants
@dekkers @underdarknl @stephanie0x00 @HeleenSG @TwistMeister @Rieven @NoemiOverdijk