Skip to main content

Philippine telcos blocking entire SMS text with internet addresses in it

If you are sending SMS texts to your friends, family or colleagues and they contain internet or web address including IP and email addresses, and even a period or dot separating, regardless of, your words and numbers, they are automatically blocked and not going to be received by your waiting recipient. Cooler heads must prevail here especially if an important message is urgently being expected. IP version 6 address is fine. However, an IPv4 including localhost address (given automatically to every computers and network interfaces as their own alone designed for troubleshooting purposes), and your money in the billion figure using dot as separators would be blocked.  If you send "local.business, naman.naman etcetera" or any words that made you use dot in between them, as part of the text, they will be blocked. There are some, that isn't blocked in this category. Like check.iclassed, some.ent, whatever.local etcetera, that is because they do not form any domain name at all

IT risks not managed, maybe violated further

It is, when you do have one or more of the following--
IT policies and procedures doesn't reflect real processes, efforts are workarounds and communications ill-defined or strict without the best of reasons.

No access verification and monitoring. Shares and lends credentials, computers and gadgets to each other. Browsing unconsciously, and wandering in, the Web. Opened emails that came from unknown individuals or sender very often without questions. Too much of a trusting person online. Uses the same flashdrive, borrowed or owned, for home computer and office computer. Update platforms and software irregularly. Very proud or dislike to cooperate with colleagues and friends or confident lone wolf. IT people enjoys computer games, doesn’t talk to business people. Risk not attended by IT and/or security people themselves.

Mad and disruptive personalities and no respect for rules and regulations. Dismissive of, or no regard to, security protocols. Inattentive to security events.

Expensive and complex solutions that nobody else is aware. IT is dealt with exclusively.

Not enough awareness or doesn't care at all. Prefer second hand information.

Believe it or not. IT risks are--may be becoming one, if not already--business risks.

While stakeholders will want to benefit from the technological development that happens in and out of their organizations, their use of IT is not without associated risks towards their business. It is an everyone’s responsibility. They must scrutinize cautiously and their actions, too. Remember, we humans, our associations, practices and data, the technology we designedly and deliberately used including the very definition and purpose of our own security and privacy rules has, or might have impending if not an immediate, risks. Within the context of revolutionary and disruptive IT environment, risk management must be solidly built within IT programs and projects, comparable to an effective security and privacy mechanisms. Not an afterthought, they say, which is true. Risk management suggests there is no such thing as unpredictable solution. Even history and current IT events says the presence of, and understanding the, risks might be the best of reasons to further the hardening of business systems.

Within our organization, risk management practices or applications and principles must ascertain common grounds and applicability. How about efficiency? Encompassing organizational policies, regulations and technical controls must be reexamined and updated once in a while. Risks must be managed.

Comments

Popular posts from this blog

[TW] IT documents, audit and leaders

IT documents comes with different names such as the following: - Manual or handbook, - Policies and procedures, - Management systems, - Project plans. In the real world we have various names with unique descriptions and purposes when in fact they could be made to do a uniform direction for which actions are based for the entire IT initiatives, probably the longest in IT lifecycle is operation. The problem is our inclination on something else which is wrong. IT remains an IT area. Business remains a business area. The same problem is carried out when we conduct IT audit. Most audit are missing the gists in which IT is being used by businesses. We once said that an effective IT audit is conducted by IT people themselves but there is something wrong with that even. Business and accounting people have been doing it with a different bias and preconceived notions which doesn't make the cut for IT direction and audit respectively. Leaders play the same game and so the problem continues an

[TW] Customers' trust and domains outside of internet's root

We all consider ourselves customers. Those who own businesses are customers even of their own. When we talk about the utility of technology, we often use customers to refer to our colleagues and some stakeholders that were provided access to our enterprise system. In business, customers are those who acquire and engage our products and services, respectively. Customers' trust is achieved and retained when we meet the expectations of our colleagues, stakeholders and the buyer of our products, services and ideas. Not only that we have assured them of those expectations in the contract or terms and conditions including some form of agreement but we attend to them sincerely when they need help. Giving them almost everything they need to form a decision. The experience must not be shallow and pretentious or they would notice whatever motive there is in between. Customers' trust is build not by the customers alone, just because we kept their experience up to their standards or we str