Shawn,
Thanks for that clarity.
Expressing the Oscap logo text to indicate report generated by is important and will build
trust.
As an end user, I want to know a tool I trust ran the report.
As an end user, the next question I have is essentially, "Are these the right
tests?"
At a simple level, that means I care about the name of the profile and WHO provided the
profile and S-CAP. If the provider is SSG that is a second branding opportunity for SSG.
(Eg: Chrome rendered my Facebook page.). With security and compliance I care more about
certifying each link in the chain.
Understanding who is providing the scanner, and who is providing the content, and who is
providing the profiles and what is inside of the profile is very hard right now. But that
is another discussion.
Mostly my point is there are at least two important branding opportunities. Also I think
all branding must be at least in the first page of any report it content display, clearly
in the summary.
Greg
301-652-9585at 12:58 AM, Shawn Wells <shawn(a)redhat.com> wrote:
> On 6/3/14, 8:12 AM, Jan Lieskovsky wrote:
> ----- Original Message -----
>> > From: "Shawn Wells" <shawn(a)redhat.com>
>> > To: "SCAP Security Guide"
<scap-security-guide(a)lists.fedorahosted.org>
>> > Sent: Tuesday, June 3, 2014 1:40:32 PM
>> > Subject: Re: [RFC] SCAP Security Guide icon to be included into
HTML guides generated by SSG?
>> >
>> > +1
>> >
>> > (Especially since users can change w/local style sheets if desired)
>> >
>> > --
>> > Shawn Wells
>> > Director, Innovation Programs
>> > shawn(a)redhat.com | 443.534.0130
>> > @shawndwells
>> >
>> > On Jun 3, 2014, at 7:11 AM, Greg Elin < gregelin(a)gitmachines.com >
wrote:
>> >
>> >
>> >
>> >
>> > I recommend going with the powered by approach on all output so SSG logo
>> > always present.
>> >
>> > Default company logo could be a "logo here" light gray placeholder
image.
> So place there just something like gray-ed out bounding box with the stub
> text "Place your company logo here" instead of including exact SSG logo
> as proposed in the subsequent reply to this thread?
>
> And should this 'grayed out default bounding box / stub' approach be
consistent
> for both 1) upstream git repo content 2) upcoming RHEL-6 package? Or is the
> approach: 1) upstream git repo content having gray-ed out image stub 2)
> RHEL-6 rpm having exact icon (one of those proposed) as proposed in the follow-up
> on this thread acceptable too? [*]
Building upon Greg's comments, there are two easy methods for "branding":
- One aspect is the default logo, (e.g. displaying SCAP-SecurityGuide-Horizontal.png
as reflected in your mock ups)
- The other is including a "powered by" footer (similar to "Generated
by OpenSCAP 1.0.8")
Government and commercial users are turning to the OpenSCAP family and replacing legacy
and proprietary tooling. OpenSCAP+SSG is becoming a brand-name scanning engine :) Having
the SSG logo included by default in upstream and RHEL6 releases is very ideal, both from a
community brand/marketing/awareness perspective, but also for a "validation of
content." ISSE/ISSO staff want to see the logo in the result printouts.
Some users, particularly System Integrators and 3PAO's, have expressed desires to
brand the scanning output. I believe documenting how to overwrite the primary logo (e.g.
with a style sheet) will meet their needs.
OpenSCAP's current footer reads "Generated by OpenSCAP ($version) on $date"
-- perhaps we could update OpenSCAP to also include the content source? Something like
"Generated by OpenSCAP ($version) on $date, using $contentSource $version"
> Thank you && Regards, Jan.
> --
> Jan iankko Lieskovsky / Red Hat Security Technologies Team
>
> P.S.: [*] Asking mainly due the reasons I am not aware of subsequent ways, how
> the benchmark could be utilized by downstream vendors. If they would want
/
> prefer just stub instead of direct image, that option should be
considered.
_______________________________________________
scap-security-guide mailing list
scap-security-guide(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide