{"id":1151,"date":"2026-11-14T12:10:00","date_gmt":"2026-11-14T12:10:00","guid":{"rendered":"https:\/\/charterkings.com\/blog\/?p=1151"},"modified":"2026-11-15T01:10:00","modified_gmt":"2026-11-15T01:10:00","slug":"identityops-charter-primer-glossary","status":"publish","type":"post","link":"https:\/\/charterkings.com\/blog\/identityops-charter-primer-glossary\/","title":{"rendered":"IdentityOps for Charter Operators: A Primer With a Glossary"},"content":{"rendered":"<p>A private charter operation lives or dies on handoffs. A broker passes a trip request to an operator, the operator assigns crew, a handler arranges ground services, a caterer receives a headcount, and every one of those parties logs into some shared system to do their part. Each login is an identity, and managing identities across so many outside parties is a discipline of its own. Technologists call it IdentityOps. This beginner primer explains what it covers, adds a mini-glossary of terms you will hear in meetings, and looks at the topic with the sober eye of someone weighing evidence.<\/p>\n<h2>Scope: what IdentityOps takes in and leaves out<\/h2>\n<p>Within the Ops Atlas, an operations-discipline catalogue edited at xOps School, the label counts as young. According to its <a href=\"https:\/\/www.xopsschool.com\/identityops\/\">entry describing IdentityOps<\/a>, there is no founding document, and suppliers apply the word to different slices of the work. The editors propose a split that beginners can hold in mind: IdentityOps is about existence and proof, meaning which accounts are real and how each one demonstrates it; a separate topic covers the rights those accounts carry; a third covers the process for requesting and reviewing raised access.<\/p>\n<p>Use a charter analogy. A passenger manifest says who is aboard. A separate document says which passengers may use which services. A third process decides how a guest gets upgraded access to the crew rest area. The first is identity, and the Atlas places the first in this discipline.<\/p>\n<h2>Mini-glossary for the first meeting<\/h2>\n<p>Here is vocabulary ordered by how soon you will meet it. Definitions are plain-language, drawn from the Atlas&#8217;s framing.<\/p>\n<ul>\n<li><strong>Identity.<\/strong> Any account that can act in a system: a person, a booking integration or a scheduled job.<\/li>\n<li><strong>Directory \/ identity provider.<\/strong> The central list of accounts and the service that confirms sign-ins for connected tools.<\/li>\n<li><strong>Single sign-on.<\/strong> A shared front door to many applications, built on standards such as SAML or OpenID Connect. Pooling sign-in in one place gathers control into that place, the Atlas argues, so guard the central service like the vault it has become.<\/li>\n<li><strong>Provisioning.<\/strong> Creating, updating and removing accounts in applications. A common standard for pushing these changes is called SCIM.<\/li>\n<li><strong>Joiner, mover, leaver.<\/strong> The three life events that should drive accounts: arriving, changing role and departing.<\/li>\n<li><strong>Second factor.<\/strong> A further proof of identity beyond a password, such as a code or a physical key.<\/li>\n<li><strong>Phishing-resistant.<\/strong> A sign-in method that cannot be handed to an impostor by trickery. The Atlas limits this label to hardware-bound credentials and smart cards.<\/li>\n<li><strong>Recovery.<\/strong> What happens when someone loses their login method. It is the most attacked step in the cycle.<\/li>\n<li><strong>Non-human identity.<\/strong> A login held by software rather than a person, for instance a flight-planning connector. These are the ones that get overlooked.<\/li>\n<li><strong>Dormant account.<\/strong> A login unused for a defined stretch.<\/li>\n<li><strong>Session.<\/strong> The live connection after signing in, which can outlast the account that started it.<\/li>\n<\/ul>\n<h2>Why charter operators have a particular exposure<\/h2>\n<p>Charter businesses share information with many outside organisations that come and go. A broker might send ten trips one month and none the next. A handler at a remote airport may need access to a trip sheet for two days. A freelance crew member may work for three operators. Each arrangement creates accounts that the operator does not employ but must still manage.<\/p>\n<p>The evidence from incidents the Atlas records points to a pattern relevant here: attackers prefer the ordinary gaps. An abandoned trial system with no second step at all. Service passwords parked in an individual&#8217;s personal storage. A help desk persuaded to reset an account. Shared third-party access is exactly where such gaps appear, because nobody on the operator&#8217;s staff feels ownership.<\/p>\n<h2>Four duties, in order of effort<\/h2>\n<h3>1. Keep an honest roster<\/h3>\n<p>List every account that can reach trip data, passenger details or payment tools, internal or external. Attach an owner and a reason to each external one. For a vendor, the owner is whoever at your company invited them. If no owner emerges, that is a finding, not a failure of the exercise.<\/p>\n<h3>2. Tie accounts to events<\/h3>\n<p>Staff accounts should follow the personnel record. External accounts should follow a contract or trip: when the engagement ends, so does the login. The Atlas insists that switching off an account is not equal to completing an offboarding, because application-level records and open sessions can remain. For third parties, set an end date at the time of creation, and renew deliberately.<\/p>\n<h3>3. Raise the standard of proof where it counts<\/h3>\n<p>The Atlas suggests starting strong sign-in with those who administer the central service, then moving to people handling email, remote access and finance, and only then to everyone. For a charter operator, the finance and dispatch teams belong in the second ring. Remember that texted codes and tap-to-approve prompts are not counted as phishing resistant in the Atlas&#8217;s reading.<\/p>\n<h3>4. Script the bad day<\/h3>\n<p>A crew member abroad has lost a phone and needs trip details immediately. That scenario is plausible every week. A written recovery routine lets staff act quickly without being talked into a mistake. The Atlas outlines self-service via a second registered method first, then human help only after a manager confirms the requester in person or on live video, with no call-backs to a number on file and a notification afterwards. Time zones make live video awkward, but they make fraud easier too, so the rule matters more, not less.<\/p>\n<h2>Reading the numbers with care<\/h2>\n<p>Beginners tend to quote a single percentage, such as the share of departed staff whose accounts were disabled. The Atlas pushes for end-to-end measurement, counting a departure as complete only when every downstream application agrees. A simple analytical habit follows from that: ask for the numerator and denominator behind each statistic and who chose them. Another habit is to compare enrolment with use. If most people have a strong method registered but a much smaller share of sign-ins uses it, the policy still tolerates the weak route.<\/p>\n<p>For targets, the Atlas floats sample service levels: a few hours for disabling the central account of a leaver, a day for all applications, ninety days to disable a dormant login plus a ceiling of three months on how long a machine credential may live. Treat these as starting points to adapt, not obligations.<\/p>\n<h2>An example trip, followed through the accounts<\/h2>\n<p>It helps to trace one imaginary trip and count the identities it touches. A broker submits a request through a portal, which creates a record under the broker&#8217;s login. The operations coordinator assigns two crew and a handler at the destination; the handler receives a time-limited view of the trip sheet. A catering vendor receives a headcount through a booking tool, and a fuel supplier receives the arrival time through an automated message sent by an integration. The finance system later pulls the trip&#8217;s cost from the same record through another connector.<\/p>\n<p>Count them: a broker, a coordinator, two crew members, a handler, a caterer, a fuel contact and at least two machine connectors. Nine identities for one flight, only three of which belong to employees. Now imagine the same exercise over a month of trips. The roster grows quickly, and without end dates the old entries linger. This is the practical meaning of the Atlas&#8217;s advice to attach an owner and an expiry to each identity: it keeps the roster proportional to the work actually in progress.<\/p>\n<h2>Where technical training fits<\/h2>\n<p>Operators rarely employ a full-time identity specialist. Often one engineer covers it alongside other duties. If you are weighing how to develop that person, material such as <a href=\"https:\/\/charterkings.com\/blog\/easy-guide-to-devops-training-and-tech-skills-in-japan\/\">an overview of DevOps training and tech skill paths<\/a> or <a href=\"https:\/\/charterkings.com\/blog\/build-your-bright-future-with-the-best-devopsschool\/\">a school-oriented look at building a technology career<\/a> may help frame the learning plan. Identity practice draws on the same scripting and automation habits.<\/p>\n<h2>A first-month plan<\/h2>\n<ol>\n<li>Build the roster, including every external party with a login.<\/li>\n<li>Set an end date on each external account.<\/li>\n<li>Issue hardware keys to administrators and finance.<\/li>\n<li>Write the lost-device script and rehearse it once.<\/li>\n<li>Time one departure from start to finish and record the result.<\/li>\n<\/ol>\n<p>Do those five things and the glossary above stops being abstract. You will know which accounts exist, who vouches for each, and how quickly you can close them. Everything more sophisticated builds on that foundation.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A beginner primer to IdentityOps for private charter operators, with an eleven-term glossary, four duties and a first-month plan for managing outside parties.<\/p>\n","protected":false},"author":6,"featured_media":1152,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[798],"tags":[],"class_list":["post-1151","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-aviation-careers"],"_links":{"self":[{"href":"https:\/\/charterkings.com\/blog\/wp-json\/wp\/v2\/posts\/1151","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/charterkings.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/charterkings.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/charterkings.com\/blog\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/charterkings.com\/blog\/wp-json\/wp\/v2\/comments?post=1151"}],"version-history":[{"count":1,"href":"https:\/\/charterkings.com\/blog\/wp-json\/wp\/v2\/posts\/1151\/revisions"}],"predecessor-version":[{"id":1238,"href":"https:\/\/charterkings.com\/blog\/wp-json\/wp\/v2\/posts\/1151\/revisions\/1238"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/charterkings.com\/blog\/wp-json\/wp\/v2\/media\/1152"}],"wp:attachment":[{"href":"https:\/\/charterkings.com\/blog\/wp-json\/wp\/v2\/media?parent=1151"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/charterkings.com\/blog\/wp-json\/wp\/v2\/categories?post=1151"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/charterkings.com\/blog\/wp-json\/wp\/v2\/tags?post=1151"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}