All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Carlos O'Donell <carlos@redhat.com>
Cc: cti-tac@lists.linuxfoundation.org,
	Siddhesh Poyarekar <siddhesh@redhat.com>
Subject: Re: [PATCH] source/faq/index: Update FAQ.
Date: Wed, 5 Jun 2024 14:33:06 -0400	[thread overview]
Message-ID: <20240605183306.GC6896@redhat.com> (raw)
In-Reply-To: <c8da333c-1734-423a-976f-d2114ce597c0@redhat.com>

Hi, Carlos -

> [...]
> > +In order to continue to support these communities we must start to adhere to
> > +the modern cybersecurity principles including moving towards zero-trust
> > +architectures with strong application sandboxing for all provided services
> > +e.g. NIST SP.800-207, separate and protect each environment involved
> > +in software development e.g. NIST SP.800-218A PO.5.1, and use multi-factor,
> > +risk-based authentication and conditional access for each environment.
> [...]

Thank you for offering those extra book references.  It would help
even more if there were an itemized list of those particular
suggestions or mandates from those books are of your interest, and how
each is absent on sourceware vs. to be satisfied at lf.  In other
words, offer a way for someone to verify problem, incompliance and
compliance.

- FChE


  reply	other threads:[~2024-06-05 18:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-29 13:48 [PATCH] source/faq/index: Update FAQ Carlos O'Donell
2024-06-05 15:41 ` Carlos O'Donell
2024-06-05 18:33   ` Frank Ch. Eigler [this message]
2024-06-11 12:18     ` Carlos O'Donell
2024-06-11 12:25   ` Carlos O'Donell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240605183306.GC6896@redhat.com \
    --to=fche@redhat.com \
    --cc=carlos@redhat.com \
    --cc=cti-tac@lists.linuxfoundation.org \
    --cc=siddhesh@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.