An Independent Security Study recommends a program. The company implements it. Then someone - the board, the CEO, the security director - decides the program isn't enough. Maybe the threat environment changed. Maybe the executive is uncomfortable with the level of coverage. Maybe the board wants more protection than the study called for and is prepared to pay for it.
The question that doesn't always get answered before the additional measures go in: what happens to the tax treatment of the portion that exceeds the recommendation?
The answer is straightforward, but it has real dollar consequences if it's not built into the planning before the expense is incurred.
The ISS sets the defensible floor, not a ceiling
The working condition fringe exclusion under §1.132-5(m) applies to security measures that are part of a qualifying overall security program established because of a bona fide business-oriented security concern. The ISS documents that concern, translates it into specific recommendations, and defines the program.
What the regulation excludes from the executive's income is the value of benefits provided in connection with that program. The program is what the study says it is.
Security measures that go beyond the study's recommendations aren't part of the qualifying program - they're additional benefits. The regulation doesn't prohibit them, and there's nothing wrong with a company providing a more extensive program than the study required. But the portion above the study's recommendations doesn't inherit the tax treatment of the qualifying program. It's compensation.
What "above the line" means in practice
The line is the study. What the study recommends is potentially excludable (assuming consistent implementation and all other requirements are met). What the study doesn't recommend is taxable.
A few examples of how this plays out:
The study recommends a residential security system and ground transportation for work-related travel. The executive requests 24-hour residential security staffing. The study determined that 24-hour protection wasn't warranted. The staffing cost above the recommended measures is a taxable benefit.
The study recommends secure ground transportation for certain travel categories. The executive prefers to use company aircraft for all domestic travel, citing general comfort with the security arrangement. The study didn't recommend non-commercial aircraft as a security measure. The value of that aircraft use is taxable.
The study covers the executive and their primary residence. The company extends the same security arrangements to a second home. The study didn't address the second residence. The security costs for the second property are a taxable benefit.
In each case, the additional measures may be entirely reasonable. The executive may have legitimate reasons for wanting more coverage than the study called for. The board may be comfortable with the additional cost. None of that changes the tax treatment of the excess.
Why this surprises people
The surprise typically comes from a category confusion: because the base program is tax-free, people assume the security arrangement as a whole is tax-free. It isn't. The exclusion is specific to measures that qualify under the regulation's requirements. Measures outside that perimeter are subject to the same rules as any other executive benefit.
The other source of surprise is timing. The measures go in first. The W-2 gets prepared later. If nobody flagged at the time that a particular enhancement wasn't covered by the study, the compensation team may not catch it until it's already been excluded - and then the correction requires either a restated W-2 or an amended return.
The clean version of this process runs in the other direction: the enhancement is identified, the tax treatment is assessed before implementation, and the compensation consequences are built into the arrangement from the start. If the company is going to provide additional security beyond the ISS recommendation, that's a known, manageable outcome - not a surprise.
The right way to structure it
When security enhancements above the ISS recommendation are part of the plan - whether driven by changed threat conditions, board preferences, or executive request - there are two legitimate paths.
The first is to update the ISS. If the additional measures are warranted by documented changes in the threat environment, the study can be updated to reflect the new facts and revised recommendations. An updated study with specific findings supporting the enhanced measures makes the full program defensible, not just the baseline. This is the right path when the facts actually support the additional coverage.
The second is to treat the excess as compensation. If the additional measures are driven by preference rather than documented threat, they're a benefit - valued, included in W-2 income, and disclosed in the proxy if they meet the materiality threshold under SEC Item 402. This path isn't a penalty; it's the structure. The company provides more security than the study required, the executive receives a taxable benefit, and the arrangement is handled cleanly in the compensation reporting.
What doesn't work is providing additional measures and treating them as part of the qualifying program when they're not. That's the position that becomes a problem on IRS examination - not because the measures were unreasonable, but because the tax treatment doesn't match what the regulation allows.
The proxy disclosure question
The above-the-line portion of a security program is a perquisite for SEC purposes if it doesn't meet the "integrally and directly related to the performance of duties" standard. Personal security enhancements provided primarily for the executive's comfort or preference, rather than as a documented business necessity, are likely disclosable under Item 402 of Regulation S-K if they exceed the reporting threshold.
This is worth flagging to compensation counsel before the enhanced measures go in, not after. A perquisite that requires disclosure in the proxy is a public disclosure. Companies that identify the disclosure obligation early can address it in the compensation committee narrative. Companies that miss it face the alternatives: restatement or explanation after the fact.
Planning the conversation correctly
The practical point is that the conversation about above-the-line security benefits belongs in the compensation planning process, not the security planning process. Security leadership can recommend whatever level of coverage they believe is appropriate. The question of what portion is tax-free and what portion is compensation is a separate question - and it needs to be answered before the program is set, not after the W-2 goes out.
If the board or executive wants more than the study calls for, that's a legitimate choice. The full cost of that choice - including the tax and disclosure consequences of the above-the-line portion - should be part of the decision, not a footnote to it.
This post is for informational purposes and does not constitute tax or legal advice. Readers should consult qualified tax and legal counsel regarding the treatment of specific programs.