Skip to content

Embedded software: Add firmware info, make it clear it applies #135

@david-a-wheeler

Description

@david-a-wheeler

Make it clear that this material applies to embedded software (as well as cloud, server-side apps, client-side apps, mobile apps, etc.), and add any material that might be needed.

I reviewed the OWASP materials here: https://scriptingxss.gitbook.io/embedded-appsec-best-practices/

We already cover practically all of it. However, there is one embedded issue that we don't fully cover: "Firmware Updates and Cryptographic Signatures":
https://scriptingxss.gitbook.io/embedded-appsec-best-practices/3_firmware_updates_and_cryptographic_signatures

We might also want to add some info from the Linux kernel self-protection work: https://www.kernel.org/doc/html/next/security/self-protection.html

We should cover that, then make it clear we're covering all kinds of software. We don't cover kernels as much, but most of the fundamentals still apply, so maybe we should instead go for "all software".

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions