Section Choosing: systems

Selections for infrastructure situations

Class first, then criteria, then names. Seven situations rather than one ranking.

Teams applying this principle can also compare practical guidance on employee time tracking app, keeping time and activity records separate from the judgement they are meant to inform.

7published
7planned
0scores out of ten
0tools we claim to have tested

Seven situations rather than one ranking. Each names the class of problem first, then the criteria that decide the outcome, and only then any products, because a product chosen before the class is a coin toss with a purchase order attached.

Three rules apply to every selection on this site. There are no scores of our own, because a score implies a measurement we have not made. There is no claim to have tested anything we have not tested. And every option carries a line describing what it costs you, including the ones we think are good.

Prices are the least stable fact in this market. Where a figure appears anywhere on this site it carries the date it was read and the source it came from; where it does not appear, that is deliberate.

Published

Further context

For a primary, standards or institutional reference, see the CIS Critical Security Controls.

Start from the class of problem, not the list of tools

Every selection here names the situation first and the criteria second. Product names come last, and each one carries the line describing what it costs you.