News for hackers. Stuff that matters.
Re:The SaaS CTO Security Checklist Redux by aahortwwy on Sunday June 06, 2021 @07:06PM (#27417188)
It's a good list, but like most (all?) of these lists it doesn't offer too much advice on organizational best practices.

IMO a security program which cannot justify its own worth to others in the organization is incomplete.

Most security professionals I've met (and I've been one of them, too) assume that security is or should be everyone's top priority. They struggle to deal with people for whom security is just one of many competing concerns.

Re:The SaaS CTO Security Checklist Redux by bitexploder on Sunday June 06, 2021 @07:38PM (#27417409)
I think recognizing that security is just one of the many engineering challenges in building software is important. It must always be prioritized and budgeted like any technical debt. It can’t be ignored, but it is rarely the supreme concern for most software. We do a lot of turn key security engineering for our customers and it’s always about prioritizing the right concerns, both from an implementation perspective and from an organizational perspective. Another thing a lot of folks struggle with is knowing where your product is and where the security fights should be at a given product and organization scale.

Risk assessment and threat modeling are huge for creating such a prioritization. Whether it’s formal and in depth or informal depends again on where things are.

Beyond these concepts, well engineered software simply has less security defects, so focusing on quality and managing technical debt often means less security debt as well.

It’s down to being an immature practitioner to think security concerns are always the primary ones. I think it’s a hard skill to master though, so I am not saying that with great judgement, someone should be a champion for security at most organizations and advocate for it. I think using empathy and curiosity goes a long way to maturing as a practitioner, but it took me many years of practice.

Re:The SaaS CTO Security Checklist Redux by gsoltis on Sunday June 06, 2021 @07:49PM (#27417471)
I agree, it is absolutely a matter of judgment and is heavily dependent on the stage and specific threats a particular organization faces. It is difficult to balance product velocity with the need to protect a growing "something to lose" that the company is accumulating.

I think one of the best things we can do as security professionals is to identify or work to create security measures that have outsized ROI and advocate for those. Using battle-tested software is one, as are, I believe, measures like MFA.

Re:The SaaS CTO Security Checklist Redux by andrewstuart2 on Tuesday June 08, 2021 @12:33AM (#27430660)
I'd also submit that one of the most important things is recognizing that ROI requires a net positive return. It's not just the time required to implement a control, you also have to factor in the opportunity cost of the increased friction. I've seen way too many times infosec organizations completely ignoring that the loss outweighs the actual risk. Hyperbolic analogy, but like forbidding driving delivery routes to avoid a parking ticket.
Re:The SaaS CTO Security Checklist Redux by jollofricepeas on Monday June 07, 2021 @01:28AM (#27419283)
Yep, this. OMG THIS!

There are three things that most security types don’t understand:

1. Security is a small component of risk. Impact (in dollars) x Likelihood = Risk

2. Cybersecurity insurance can change the risk equation dramatically

3. It is possible for a security remediation to kill/harm more people than the underlying insecure system that the fix is being applied to

Once you realize that security is a risk problem then you’re able to quantify that problem in dollars. Lives affected can be used as a metric too but dollars are the magical language that everyone can understand.

Re:The SaaS CTO Security Checklist Redux by rjzzleep on Monday June 07, 2021 @03:15AM (#27419912)
I just went through a "risk triage" they called it for a client and while the client is more focused on being able to work AT ALL the risk triage is solely focussed on the monetary damage of losing IP and data.

Two things:

1. Security to some extent doesn't always need to impede engineering. Enterprise IT security is very much focused on removing risky behaviour, without providing any alternatives.

2. The cost to the business losing IP it cannot generate due to excessive security practices should be taken into account when doing these exercises.

I'd argue that the security part of this organization has gone "rogue" and is solely focused on justifying its own existence. It's as if the security part is more focused on reducing liability for itself than it is on actually securing systems.

That said, I still think that most organizations put too little emphasis on security, not too much. And oftentimes, too late.

EDIT: an analogy I like to use is that oftentimes these people try to build a castle surrounded by massive walls without doors or gates, but since people inside still have to get things from the outside they just dig a tunnel circumventing the whole thing. But since it wasn't approved there is no liability problem for the security part of the org.

Re:The SaaS CTO Security Checklist Redux by austinjp on Monday June 07, 2021 @02:13AM (#27419561)
Fully agree that impact x likelihood = risk, although I'd extend it beyond dollars. Impact can include reputation, health, etc. Certainly these could be measured using cash-value as a proxy, but this risks chasing the wrong metric.

I also recognise that "when a measure becomes a target it ceases to be a good measure", and cash as the bottom line risks increasing this tendency.

Too idealistic, probably :)

Re:The SaaS CTO Security Checklist Redux by aahortwwy on Monday June 07, 2021 @03:28AM (#27419992)
Using cash-value as a proxy for impact gives you many benefits. Here are two particularly good ones that are relevant to planning security work:

1. It clarifies your thinking around impact. The simple exercise of sitting down and trying to put a dollar amount on the reputation damage your organization would suffer if Bad Thing were to happen will help you better understand the likelihood and potential consequences of Bad Thing.

2. It allows for more easy comparison to the costs that will be incurred while mitigating the risk. If you think the impact of Bad Thing will be "significant reputation damage", that's bad, but it doesn't help you decide how much time, effort, and money you ought to dedicate to preventing Bad Thing.

Blindly chasing metrics can lead to pathological behaviour, for sure, so you need to balance that with strong cultural values, but overall I would say the security industry is terribly heavy on cultural values right now and pays little to no attention to measuring what actually matters to organizations.

Re:The SaaS CTO Security Checklist Redux by faeyanpiraat on Monday June 07, 2021 @02:36AM (#27419674)
Corps don’t care about your health, they care about you being healthy enough to bring in the dough.

And when you accept this fact, you can skip lamenting about all sorts of ethical questions and just know that everything will be a monetary decision in the end.

Re:The SaaS CTO Security Checklist Redux by Kalium on Monday June 07, 2021 @07:03AM (#27421151)
I've found that using a risk-based approach to security requires a mature organizational framework for handling risk. A mature risk management process keeps good records of how risks are handled, what the estimated impact and likelihood are, will promote accountability, and will learn when risks are realized.

An immature one, of the sort many companies have, may have difficulty with some or all of these steps. Often the immaturity is invisible until it's too late - an impact or likelihood is far higher than estimated (and thus your quantification was wildly off and you took your estimate too seriously), there's no organizational accountability (so nobody who makes serious mistakes has to learn from it), and so on.

I don't know how many SaaS startups have mature risk management processes, but I know I've seen companies well beyond the startup stage that suffer from immature ones.

Re:The SaaS CTO Security Checklist Redux by kenniskrag on Monday June 07, 2021 @02:08AM (#27419529)
> Cybersecurity insurance can change the risk equation dramatically

Do they check if you implement best practices in security? I could imagine, that this will have an impact on the premium.

Re:The SaaS CTO Security Checklist Redux by windowsworkstoo on Monday June 07, 2021 @03:02AM (#27419838)
Yes and the audits around this change arbitrarily each year and you will be denied coverage if you are doing something otherwise competent but miss their particular flavour of the year
Re:The SaaS CTO Security Checklist Redux by sublimefire on Monday June 07, 2021 @06:23AM (#27420908)
An interesting parallel is how these similar issues are solved in other engineering domains. In civil engineering you have heavy regulation and accountability. If a building falls then the engineer is responsible and she could get a jail sentence. To prevent buildings from falling there are regulations around minimum requirements, audits, material quality, etc.

Regulation in software "does not exist" as the actual threat is minimal. If your program crashes then nobody dies ('m not talking about rockets). Therefore it always looks like security people always have temper tantrums as there is no meaningful quantifiable risk.

In our org we ended up asking pentesters to get into the systems instead of just giving us an automatically generated report that contains links to CVEs. If they cannot use existing risks to get into the system then that risk is trivial.

Re:The SaaS CTO Security Checklist Redux by berkay on Monday June 07, 2021 @07:13AM (#27421212)
Good point. There are also some software solutions (picus security, etc.) that tests your validates whether your environment is exposed due to specific CVEs. It's a good way to prioritize which vulnerabilities that you should tackle first.
Re:The SaaS CTO Security Checklist Redux by raesene9 on Monday June 07, 2021 @05:19AM (#27420561)
My reading of this list is that it's not designed to be a starting point for a full security programme, but a starting point for small organizations who don't even have a security function yet.

In an ideal world, every company would have dedicated resource for this and a well targeted/justified programme of work, but I think there's quite a few where responsibility falls on the CTO and there lists like this can be useful.

Re:The SaaS CTO Security Checklist Redux by aahortwwy on Tuesday June 08, 2021 @06:58PM (#27442173)
This list and others like it are for sure useful, but the CTO of a smaller organization still needs to be able to:

- Prioritize items on this list relative to each other.

- Prioritize items on this list relative to other work.

- Communicate the reasons for that prioritization to other members of leadership, at least.