Skip to content
English
  • There are no suggestions because the search field is empty.

Getting Started With Security Resources

Security Resources are the inventory of what your organisation actually runs, owns and relies on, and they are what your controls, business systems and threat simulations are evidenced against.

Security Resources, under Catalogue > Security Resources, is your record of the things that make up your security posture: the technology you run, the people who operate it, the providers you depend on, and the documentation that governs it. It matters because almost everything else in CyberHQ eventually points back to it. A control is credible when a resource evidences it, a business system is meaningful when you know what it is built from, and a threat simulation can only produce a financial case when the resources involved carry costs.

The four types of resource

Every resource is one of four types, and the type determines what you record against it:

  • Technology covers software, hardware and infrastructure. Your firewalls, your endpoint protection, your logging platform. Its sub-types are Network And Infrastructure Security, Web Security, Endpoint Security, Application Security, Data Security, Mobile And Device Security, Governance Risk And Compliance, Security Operation And Incident Response, Threat Intelligence, Email And Messaging Security, Iot Ot Security, Fraud, Cloud Security and Other.
  • People covers roles and staff who perform a security function, whether that is a dedicated security team or someone carrying the responsibility alongside another job. Its sub-types are Full-Time Employee, Part-Time Employee, Contractor and Other.
  • Service Providers covers the third parties who deliver part of your security for you, such as a managed detection provider. Where you also assess that provider as a vendor, you can link the two so the assessment and the dependency sit together. Its sub-types are Internal Service Provider, Managed Security Service Provider, External Consultant, Application Service Provider and Other.
  • Documentation covers the policies, standards and procedures that govern how the rest of it works, and the other documents that support them. Its sub-types are Policies, Standards, Processes And Procedures, Guidelines, Certifications, High-level Design Document, Playbook, Report, User Guide, Proposal, Presentation, Manual, White Paper, Project Plan and Other.

Every resource has a sub-type, chosen when you add it. It narrows down what kind of resource this is, and you can filter the list by it.

The split matters because it changes what a resource can evidence. A policy document is the right evidence for a governance control in a way that a firewall is not.

Working in the Security Resources page

The page has a tab for each type of resource, Technology, People, Service Provider and Documentation, and an Archived tab for resources you have archived. The Document Classification tab creates Documentation resources from your own files; see How to Add and Edit a Security Resource.

Each tab lists its resources in a table. By default the Technology tab shows Name, Sub-Type, Tags, Criticality, End Date and Entity. The People, Service Provider and Documentation tabs show Name, Sub-Type, Tags and Entity, and the Documentation tab adds Method.

The Method column shows how each document was added: Manual upload if someone added it through the form or a CSV upload, or Scanned if Document Classification created it. Hover over it to see the document's category and method, who added it and when it was created. Method is blank for resources brought in by a connector and for older resources added before it was recorded.

Resources that CyberHQ creates automatically, such as those it creates for your business systems, are marked (automated) after their name. An end date that has passed is shown in red, so lapsed licences and contracts stand out.

To change the columns, click Select columns and tick the ones you want. You can choose from Name, Resource Type, Sub-Type, Method, Description, Tags, Criticality, Approval Date, End Date, Created On, Entity and Other Fields, and turn the row selection checkboxes on or off. The Action column, which holds each row's buttons, is always shown.

Clicking a row does not open the resource. Use the buttons in its Action column instead: the pencil opens the resource for editing, and the folder opens its attachments.

What to record, and why it pays off later

Beyond a name and description, three fields do more work than they first appear to:

  • Criticality tells you and everyone else how much the organisation depends on this resource. It is what lets you answer "what matters most here" without reading the whole inventory.
  • Cost is what makes financial modelling possible. A resource can carry a purchase or capital cost, an ongoing operating cost and a one-off non-recurring cost. Threat simulations use these to produce a return on investment figure, so a resource with no cost recorded contributes nothing to that calculation. If you intend to use Threat Modelling to justify spend, record costs as you go rather than retrofitting them later.
  • End date (the Expiry Date on Documentation) drives renewal reminders, covered below.

For People resources you can additionally record what they are responsible for, which technology they operate, how many days a week they are available, and whether they are key personnel. That last one is worth using honestly: it is how you surface a single point of failure that happens to be a person rather than a system.

Renewal and expiry reminders

Every resource can carry an end date: the End Date on Technology, People and Service Provider resources, and the Expiry Date on Documentation, which also records when the document was approved as its Approval Date. The end date is what turns your inventory into something that tells you when to act rather than something you have to remember to read.

Where reminders are enabled for your workspace, CyberHQ sends a warning ahead of the date and a further notice once it passes. By default the warning arrives 90 days before expiry, which suits annual licences and contracts.

Three details are worth knowing:

  • Reminders go to the resource's owner, and the expiry notice goes to your administrators as well. A resource with no owner sends everything to your administrators, so assigning owners is what stops renewals becoming one person's problem. Only Technology and Documentation resources have an Owner, so reminders for People and Service Provider resources always go to your administrators.
  • Extending a date re-arms the reminders. Push an end or expiry date into the future and both notices reset, so a renewed contract warns you again next cycle without anything to reconfigure.
  • Reminders always appear in your CyberHQ notifications. Whether they are also emailed to you depends on the Resource option in your email notification settings.

Bringing resources in, and getting them out

You can add resources one at a time, upload many at once from a CSV template, create Documentation resources from your own files with Document Classification, or link a connector to your CyberHQ workspace to import them from an external platform. Each route is described in How to Add and Edit a Security Resource. Export works the same way in reverse, which makes bulk editing practical: export, edit the spreadsheet, upload it back. See How to Export your Data to CSV.