Predicate Proposal CSO (Chief Security Officer)

CSO
Value statement: The CSO provides executive leadership and oversees the identification, assessment and prioritization of risks, directing all efforts concerned with the security of the organization.
What does CSO do:
Ensures the security of the business as a whole.
Provides physical, property, financial, information security.
Develops and implements security and risk mitigation strategies.

Definition: A Chief Security Officer (CSO) is an organization’s most senior executive accountable for the development and oversight of policies and programs intended for the mitigation and/or reduction of compliance, operational, strategic, financial and reputational security risk strategies relating to the protection of people, intellectual assets and tangible property.
Tooltip definition of the predicate: “The CSO of an organization”
Type of value: Entity
For enums - all possible values: N/A
of accepted values: One
Inverse Properties and Name: ‘CSO of’
Examples of proper use:
‘Verisign’ → ‘CSO’ → “Danny McPherson”
citation:Danny McPherson - Executive Vice President and Chief Security Officer (CSO) - Verisign . This citation points to an official website Verisign
Examples of improper use:
‘Verisign’ → ‘CSO’ → ‘Danny McPherson’ citation: https://wing.splashthat.com/ . Danny McPherson Summit participant
Usage in other schemas:
Usage in wikidata: chief security officer - Wikidata 1
Usage in schema.org: N/A
Constraints: Entity should have value ‘is a’ → ‘Person’
Masculine/Feminine Form: N/A
Restrictions (ie PII concerns): N/A

CSO of

Value statement: The CSO provides executive leadership and oversees the identification, assessment and prioritization of risks, directing all efforts concerned with the security of the organization.
Definition: A Chief Security Officer (CSO) is an organization’s most senior executive accountable for the development and oversight of policies and programs intended for the mitigation and/or reduction of compliance, operational, strategic, financial and reputational security risk strategies relating to the protection of people, intellectual assets and tangible property.
Tooltip definition of the predicate: “Organization a person is CSO of”
Type of value: Entity
For enums - all possible values: N/A
of accepted values: One
Inverse Properties and Name: ‘CSO’
Examples of proper use:
‘Danny McPherson’ → ‘CSO of’ → ‘Verisign’, citation:Danny McPherson - Executive Vice President and Chief Security Officer (CSO) - Verisign. This citation points to an official website Verisign
Examples of improper use:
‘McPherson’ → ‘CSO of’ → ‘Wing Security Summit’ citation:https://wing.splashthat.com/ . Danny McPherson Summit participant
Usage in other schemas:
Usage in wikidata: CSO of - Wikidata
Usage in schema.org: N/A
Constraints: Entity should have value ‘is a’ → ‘Organization’
Masculine/Feminine Form: N/A
Restrictions (ie PII concerns): N/A

Generally we want to move away from having a separate predicate for each potential title in an organization - the exception to that probably being the CEO. It’s a slippery slope from a few CxO titles that make sense, to the next 100 CxO titles that various companies are making up / using. And then after that, what about the VP roles, etc?

Our current intention is to capture the roles that individuals are filling with qualifiers. So:

  • {$PersonA} → [employed at] → {$CompanyA} with the qualifier → [job title] → {CwhateverO}

This is fundamentally more sustainable than an individual predicate for hundreds of different jobs.