Connect with us

Accounting

TIGTA faults IRS on data security, cloud security in separate reports

Published

on

The Treasury Inspector General for Tax Administration, in two reports, critiqued the IRS on cybersecurity for both its data warehouse and its cloud infrastructure.

Data warehouse security

One report specifically pertained to the IRS’s Compliance Data Warehouse, effectively a massive data warehouse containing multiple years of federal tax information and personally identifiable information consolidated from multiple sources, internal and external to the IRS. The CDW offers a broad range of databases that research analysts may access through a variety of data analytic tools. This includes things like Individual Master File data, Business Master File data, tax return data, taxpayer contact information, conversations between a taxpayer and an IRS agent, and actions that took place on behalf of the IRS. As one might imagine, the IRS considers it very important for this data to remain secure. This is why it is required to record audit trails in the system’s security documentation for indications of inappropriate or unusual activity. However, TIGTA said the tools used to visualize audit trails associated with the Event ID data field, specifically CDW logins, failed to accurately display the login data field, with the result that the available login data were both incomplete and unreliable. For example, TIGTA found that from March 2023 to July 2023, the repository was not displaying any audit trails that contained CDW login information at all.

TIGTA said this can be attributed to two root causes. First is that, within the CDW Platform Audit Worksheets, the coding script used to identify system logins in the CDW logs was referencing an incorrect file name. Upon recognizing the error, IRS alerted the appropriate cybersecurity officials and continued to collaborate to identify and implement a resolution. Second, when the login information search period is greater than 90 days, the search does not return complete and accurate login information. As of April 3, 2024, the exact cause of this error was still unknown; however, cybersecurity officials are continuing to troubleshoot the issue. The IRS reports that restricting the search to 90 days or fewer helps manage performance and response time, given the sheer volume of CDW log data. The IRS plans to add a note to the audit trail repository to advise about the 90-day limitation and noted that multiple searches for 90 days or fewer may be run.

Further, TIGTA said that while actionable events require timely review to determine if additional escalation or notifications are needed, the Compliance and Audit Monitoring team is not reviewing any of them. A management official stated that CDW’s actionable events are not being reviewed because of a miscommunication between the Compliance and Audit Monitoring team and CDW personnel, and that the team began the review of all required actionable audit events in March 2024. Further, TIGTA said the monitoring that is being done is highly inefficient, as the IRS’s audit trail repository does not permit users to export or download multiple auditable or actionable events at the same time. As a result, the team is restricted to reviewing, analyzing and reporting on singular audit events. 

TIGTA did, however, concede that all 1,173 CDW users as of April 2024 completed each of the four mandatory training courses. However, mandatory training requirements for unpaid hires (academic researchers and student volunteers) were not managed via the Integrated Talent Management system. According to management officials from the IRS’s Human Capital Office, this limitation was due to an integration issue within the agency’s human resources system. While TIGTA found that the current manual process for tracking training requirements for unpaid hires is functional, it does not afford any type of verification that the training was actually completed. 

TIGTA recommended that: 1) the IRS’s chief data and analytics officer ensure the agency’s audit trail repository accurately displays and reports all CDW login information; 2) the chief information officer ensure that all required actionable audit events for the CDW are reviewed; 3) the CIO ensure that automated mechanisms are incorporated into the actionable audit event escalation process; 4) the CIO and chief data and analytics officer ensure that identified vulnerabilities are timely remediated; and 5) the chief data and analytics officer ensure that all CDW servers are included in configuration compliance scans. The IRS agreed with all five recommendations. 

Cloud infrastructure security

TIGTA, in another report, faulted the IRS for its cloud security assessment, approval and monitoring process, saying it was not maintaining appropriate separation of duties for certain roles related to cloud systems, and did not follow guidance meant to prevent conflicts of interest, increasing the risk of erroneous and inappropriate actions.

Specifically, inspectors determined that 35 (70%) of the 50 cloud systems reviewed had the same individuals assigned as either the authorizing official or the AO’s designated representative and system owner. The remaining 15 (30%) of the 50 cloud systems reviewed demonstrated appropriate separation of duty with different individuals assigned as the AO or the AO-designated representative and system owner. 

While the National Institute of Standards and Technology guidelines recommend that organizations ensure there are no conflicts of interest when assigning the same individual to multiple risk management roles, there was no IRS policy statement that specifically prevented the roles from being occupied by the same person. After this issue was brought to management’s attention, IRS officials stated they will review the NIST guidance and work to ensure that updates are made as appropriate to have different individuals occupy these roles. 

TIGTA also noted that the IRS was not preparing summary reports for 11 (22%) of 50 cloud systems every month as required. The Cloud Continuous Monitoring Strategic Operating Plan requires cloud  information system security officers to prepare a monthly summary report for each of their assigned systems and provide it to the system’s AO. Further, summary reports for 45 of the 50 cloud systems identified that the reports were missing required information. Also, 31 of the 45 cloud systems reviewed were missing the trackable Plan of Action and Milestones weakness identification number on the summary report. And security documents were missing approvals or were not properly approved within the Department of the Treasury data repository. Specifically, the repository was missing five (10%) of the 50 cloud systems’ Authorization-to-Operate memorandums. Finally, 15 of 50 cloud systems were missing required  Federal Risk and Authorization Management Program Security Threat Analysis Reports. 

TIGTA recommended that the IRS’s chief information officer ensure that: 1) separation of duty controls reflect guidance and require that all cloud systems have a unique System Owner and Authorizing Official; 2) an Authorization-to-Operate memorandum is approved for the system to remain in production; 3) summary reports are timely created; 4) procedures are updated; 5) management approvals are consistent and documented; and 6) the Cloud Security Assessment and Authorization process is completed annually. The IRS agreed with four recommendations and plans to ensure separation of duty controls reflect guidance; the system obtains authorization; that summary reports are timely created; and that management approvals are documented. The IRS disagreed with two recommendations, stating its weakness summary reporting is sufficient without unique identifiers and that cloud security assessments are completed in accordance with existing procedures.

Continue Reading

Accounting

Mandatory ESG Reporting Standards Demand Standardized Non-Financial Audit Trails

Published

on

Mandatory ESG Reporting Standards Demand Standardized Non-Financial Audit Trails

Corporate accounting departments face an expanded regulatory mandate as mandatory sustainability and Environmental, Social, and Governance (ESG) reporting frameworks take full effect internationally. Governed by the European Union’s Corporate Sustainability Reporting Directive (CSRD) and the International Sustainability Standards Board (ISSB) IFRS S1 and S2 standards, enterprise financial controllers are now legally required to track, verify, and report non-financial data with the same internal controls and auditability as traditional financial statements.

The expansion shifts ESG compliance

This regulatory expansion shifts ESG compliance from marketing departments to corporate accounting offices. Financial managers are now responsible for gathering, consolidating, and verifying carbon emissions metrics, supply chain labor conditions, water usage, and climate risk exposures across multi-tiered corporate structures. These non-financial metrics must be integrated into standardized general ledgers to withstand rigorous third-party audit assurance processes.

To comply with these rigorous reporting mandates, accounting software providers have added dedicated ESG modules designed to aggregate data from IoT sensors, utility platforms, and vendor management systems. Controllers are implementing internal control frameworks—modeled after traditional COSO frameworks—to ensure the completeness, accuracy, and consistency of sustainability disclosures, protecting organizations against greenwashing penalties and litigation risks.

The transition requires significant cross-functional collaboration between accounting teams, legal counsel, and operational directors. Accounting professionals are expanding their technical expertise beyond financial ledgers to master carbon accounting methodologies, lifecycle assessment standards, and non-financial data governance protocols, fundamentally expanding the role of the modern corporate accountant.

Why This Information Matters
Mandatory ESG disclosures require companies to treat environmental and social metrics as audited financial records. Executives, accountants, and board members must institute formal tracking and assurance processes to satisfy legal mandates, maintain investor confidence, and mitigate regulatory non-compliance risks.

Continue Reading

Accounting

SEC’s Semiannual Reporting Proposal Faces Investor Pushback: What CFOs Need to Know

Published

on

U.S. Securities and Exchange Commission (SEC)

A proposal from the U.S. Securities and Exchange Commission to potentially shift some public companies away from quarterly financial reporting toward a semiannual model is drawing significant pushback from investors, even as it continues moving through the regulatory process. The debate has direct implications for corporate finance teams, auditors, and the broader transparency of U.S. capital markets.

What the SEC Proposed

According to a summary published by accounting advisory firm Cohen & Co., the SEC issued a proposed rule on May 19, 2026, aimed at simplifying financial reporting requirements for many U.S. public companies. The proposal would potentially reduce the frequency of certain mandatory disclosures from quarterly to semiannual, a structural change that has not been made to core U.S. reporting requirements in decades.

The proposal follows an extended debate within U.S. policy circles, with proponents arguing that reduced reporting frequency could lower compliance costs and free up management time for longer-term strategic planning rather than quarter-to-quarter results management.

Why Investors Are Pushing Back

Comment letters submitted in response to the proposal have been extensive, and according to Cohen & Co.’s review of the public record, investors “appear to be largely opposed” to the shift, viewing frequent interim reporting as a core benefit of U.S. capital markets relative to other jurisdictions.

Accounting and law firms have taken a more measured position, generally urging any changes to remain aligned with the Financial Accounting Standards Board (FASB), whose existing disclosure requirements and guidance are built around a quarterly reporting cadence. A shift to semiannual reporting without corresponding changes to FASB guidance could create friction between SEC filing requirements and GAAP-based disclosure expectations.

Lessons From the U.K. Experience

The debate is not without precedent. The United Kingdom moved away from mandatory quarterly reporting for listed companies in 2014, returning to a semiannual disclosure requirement. According to Cohen & Co.’s analysis, that experience offers a cautionary data point: there was no measurable increase in capital expenditure or R&D investment following the change, while analyst coverage of affected companies declined as reliable interim information became less available — a particular risk for smaller and newly public companies that rely on analyst coverage to maintain investor visibility.

Practical Implications for Finance Teams

Beyond the debate over disclosure philosophy, the proposal carries practical complications. Many companies have debt covenants and credit agreements structured around quarterly financial delivery; a shift to semiannual reporting could require renegotiating those terms. Reduced reporting frequency would also extend the “window of market silence” between disclosures, a factor that governance and investor-relations teams would need to manage carefully to avoid information asymmetry.

Separately, and unrelated to the reporting-frequency debate, the SEC and FASB have continued finalizing more routine updates this year. New Accounting Standards Updates are taking effect for December 31, 2026, fiscal year-ends covering income tax disclosures, credit loss measurement, induced debt conversions, and stock compensation, according to Eide Bailly’s review of 2026 ASU activity. Additional guidance on paid-in-kind dividends and environmental credits is also on the near-term horizon.

What to Watch Next

The semiannual reporting proposal remains in the comment and review phase, and no final rule has been adopted as of this writing. Finance leaders should monitor the SEC’s regulatory agenda for further movement, while treating the current quarterly reporting requirement as the operative standard until any final rule is issued and an effective date is set.

Given the extent of investor opposition documented in the comment file, a full shift to mandatory semiannual reporting appears more likely to result in either a scaled-back compromise or continued study rather than swift adoption — though the SEC’s ultimate direction remains uncertain.

 

Continue Reading

Accounting

AI-Driven Automation and Continuous Accounting Frameworks

Published

on

The accounting profession is undergoing a fundamental structural transition as enterprise finance departments shift from periodic month-end closes toward automated continuous accounting models. By integrating specialized machine learning algorithms directly into enterprise resource planning (ERP) platforms, chief accounting officers are transforming financial reporting from a retrospective exercise into a real-time operational asset.

The Shift from Periodic Close to Continuous Financial Reporting
Traditional accounting workflows heavily relied on manual data reconciliation, spreadsheet calculations, and multi-week closing cycles at the end of each fiscal period. In contrast, continuous accounting frameworks utilize automated software agents to process, validate, and post transactional data in real time as business activities occur.

Automated bank reconciliation tools cross-reference incoming bank feeds, invoice records, and purchase orders automatically. By resolving transactional variances instantly throughout the month, corporate accounting teams eliminate the traditional workload spikes associated with quarterly and annual closes.

Machine Learning in Audit Trails and Anomaly Detection
Advanced natural language processing (NLP) and machine learning tools are redefining internal audit and financial control environments. Automated systems analyze 100% of general ledger entries, identifying anomalous transactions, duplicate payments, and unauthorized journal entries in real time.

Rather than relying on random statistical sampling, corporate internal auditors can focus their attention on high-risk flags automatically surfaced by algorithmic monitoring platforms. This continuous risk assessment strengthens internal controls over financial reporting (ICFR) and significantly reduces fraud risk.

Evolving Roles for Accounting Professionals
As routine data entry and manual reconciliation tasks become fully automated, the skill set required for accounting professionals is shifting toward data analysis, system design, and strategic business advisory.
– Systems Governance: Accountants are increasingly responsible for monitoring algorithmic accuracy and managing data integration pipelines.
– Business Partnership: Finance professionals leverage real-time financial dashboards to advise operational leaders on margin management and working capital allocation.
– Regulatory Compliance Management: Accounting teams utilize automated platforms to ensure compliance with dynamic tax codes and international accounting standards.

Core Implementation Recommendations
1. Deploy Automated Reconciliation Tools: Integrate continuous transaction processing modules into existing enterprise ERP architectures.
2. Establish Algorithmic Governance Controls: Implement strict internal testing protocols to ensure automated accounting rules comply with GAAP/IFRS standards.
3. Reskill Accounting Teams: Invest in training finance staff on data analytics, workflow automation, and predictive financial modeling.

Continue Reading

Trending