Proposal: isHardened should not be a property on its own about pytm HOT 11 OPEN

True. Let's do it.

from pytm.

What would be a proper dictionary of properties and their values? For example,

runsAs = (Root, Administrator, User, Nobody)
exposes = (HTTP, HTTPS, ...) ?

I believe this might be more extensible than a ton of on/off switches, thoughts?

from pytm.

Is the OS patched is another property to look at. I guess to answer the list of properties required, we need to look at when exactly we think a system is considered hardened? What are the criteria or things to look for at minimum?

from pytm.

from pytm.

But do we have to go itemized? Or could we get away with something that refers to the process, as in

isHardened = ("No", "Planned", "Yes")

At the end of the day I believe we want developers to be able to write the description code on the fly, and should strive to have only as much detail as necessary, to avoid having to go to documentation, etc.
Perhaps we should have objects self-check for completeness at runtime, suggesting fields that need more information before running the threats?

from pytm.

Yeah this makes sense to me. Keeping it simple.

from pytm.

I moved the current attributes into Python "@Property". We need to decide if we want to leave everything open or if we want to use enumerations for certain values. I'm inclined to follow MSFT in the choices, but only up to the point where we get 1::1 functionality with their tool, and then we start opening up further and going farther. Ideas?

from pytm.

Sounds good to me.

from pytm.

Got some feedback from potential users - the issue of granularity is important. I suppose it would be great if we could come up with threats that happen at many levels, as in "is it hardened? yes/no" leading to a "it should be hardened" threat, but then smaller granularity questions like "is it patched" and "does it have more services than needed" (just throwing it out there....) lead to "it is not hardened" that then leads to "it should be hardened".

from pytm.

Related to #113 re: inherited properties or state.

from pytm.

Have been thinking about derived properties for an incubation effort. Will look to mock something up.

from pytm.