Too Late?
I'm not sure why MIT's attachment-blocking is making news now ("MIT: Executables Be Gone!," BuzzCut, Nov. 13, 2003). It's too little too late to stop the virus/worm problems we've seen over the past year. If more people had banned attachments years ago, viruses would be almost nonexistent now. My company banned most attachments more than three years ago.
Terabyte Computers
Brian Bergin
President
 |
Getting IT In Line
I appreciate Rob Preston's assessment of the issues separating an IS department and the rest of an organization ("A Bridge Too Far?," Oct. 30, 2003). Aligning the IS department with the company's goals and objectives appears to be a consistent challenge for many of my peers.
I have yet to converse with a peer whose organization lacks business goals and objectives or a strategic plan that outlines where the company is expected to be in the next five years. On the other hand, I have yet to hear a colleague say his or her IS department identified technologies that support those objectives, prioritized which technologies offer the greatest ROI or bring the organization closer to its goals, and then condensed the findings into an IS strategic plan, which could be used for budgeting, resource requirements, policies, standards, operational procedures and, perhaps most important, answering the CEO's questions before they are asked.
To realize the benefits of cloud-native software, an application must actually be cloud-native—designed to run in the cloud, interacting with disaggregated cloud services, fully manageable as code—to deliver the expected benefits.
By combining resources and expertise, the AI-Enabled ICT Workforce Consortium will offer a blueprint for how industries can adapt to an AI-dominated future.
IT leaders should heed the guidance of cybersecurity insurance providers who think businesses should prioritize security education, incident preparedness, regular internal audits, and ongoing vulnerability scanning and patching.
